Can anyone explain why the Campaign Run Data Action returns a 403 Forbidden error when attempting to create a ServiceNow incident from an outbound call disposition? The Architect flow is configured to trigger on Call Disposition Set. The webhook payload is structured exactly as per the ServiceNow REST API documentation for incident.do, including the mandatory caller_id and short_description fields. Debugging the flow execution in Genesys Cloud shows the Data Action receiving a 200 OK from the internal validation but failing at the external endpoint. The ServiceNow instance is running Tokyo (v14.2). We are using a Service Account with admin role for the basic auth credentials in the Data Action configuration. Interestingly, manual POST requests to the same endpoint via Postman succeed without issue, suggesting the Genesys Cloud outbound IP range might be blocked by the ServiceNow firewall rules or the OAuth token scope is insufficient for this specific integration type. The error response body is empty, which makes troubleshooting difficult. Are there specific headers required by the Genesys Cloud outbound dialing module that are being stripped before the request hits ServiceNow?