Is there a clean way to configure BYOC webhook routing for ServiceNow integration?
The Genesys Cloud outbound campaign triggers the Data Action, but the HTTP POST to the ServiceNow REST API endpoint fails with a 403 Forbidden error. The payload contains the correct org_id and valid OAuth scopes as per the multi-org documentation, yet the BYOC edge node drops the request before it reaches the destination.
Inspecting the network traces shows the request originates from the correct virtual IP, but the ServiceNow firewall rejects it due to missing headers. The webhook configuration in Genesys Cloud v24.4.0 does not expose a field to inject custom headers directly into the BYOC payload, causing the correlation to fail.