ServiceNow Webhook 403 Forbidden on GDPR Data Purge Trigger

I’m curious as to why the webhook.execute node returns a 403 Forbidden when invoking the ServiceNow REST API for GDPR data deletion via Architect? The OAuth token is valid for 24 hours, yet the request fails immediately upon hitting the table.delete endpoint.

The payload structure matches the ServiceNow documentation exactly, and the same credentials work in Postman. This happens exclusively for digital channel conversations routed through the compliance flow in Release 2024-12 (v13.2).

Need to confirm if Genesys Cloud imposes additional scope restrictions on webhook headers for sensitive data operations or if this is a ServiceNow side configuration issue.