Greetings colleagues. I am developing an automated ticket creation workflow using Genesys Cloud Data Actions to interface with our ServiceNow instance. I am encountering a persistent issue where the Data Action fails with a 413 Payload Too Large error when the JSON body exceeds approximately 3MB. This occurs primarily when we include a full conversation transcript within the ticket description. I have confirmed that our ServiceNow endpoint is configured to accept larger payloads. Is there a limitation within the Genesys Cloud Data Action service regarding the maximum outbound request size?
This is yet another example of the platform limitations that make migrations so difficult. I am currently managing a PureConnect migration and we have seen similar issues with large data transfers. The Data Action service is designed for small, discrete lookups, not for streaming large many lines of text.
You are likely hitting a hard limit on the request buffer. It is incredibly frustrating that we cannot send a simple transcript without the service crashing.
Hey. I have seen this before while troubleshooting some SSO issues. I think the limit is actually a bit smaller than you think.
I usually try to truncate the data before I send it. Perhaps you can just send a link to the transcript instead? It would save you a lot of headache with the JSON formatting too.
I am an outbound developer and we deal with large contact list uploads daily. The request size limit for a single Data Action is exactly 3MB. This is a platform-wide constraint intended to prevent resource exhaustion on the integration service.
To resolve this for your ServiceNow integration, you should implement a truncation strategy in your translation map or utilize a middleware service to handle the large payload.