The Data Action is consistently returning a 400 Bad Request from ServiceNow (/api/now/table/incident) with the message: Invalid JSON payload: Unexpected token < in JSON at position 0.
The integration uses a standard HTTP POST from a Genesys Cloud Architect flow (v2024-04.0) triggered by a Digital Channel message event. The payload is constructed via a Data Action mapping, converting the message.text attribute into the short_description field. Headers include Content-Type: application/json and Basic Auth.
Debug logs show the outbound request body appears correct:
{"short_description": "Customer inquiry about billing"}
However, the response body from ServiceNow contains HTML:
<html><body><h1>400 Bad Request</h1>...</body></html>
This suggests ServiceNow is rejecting the request before parsing the JSON, likely due to a malformed header or content length issue introduced by the Genesys webhook handler. Direct testing via Postman with identical headers and payload succeeds.
Has anyone encountered issues with Genesys Data Actions appending hidden characters or malformed headers to digital channel triggers? Are there specific limitations on payload size or character encoding for digital channel events that might cause the server to return HTML instead of a JSON error?