Pushing complex incident data from Genesys Cloud to ServiceNow via a Data Action is failing with a 422 Unprocessable Entity. The endpoint works in Postman, but the Architect flow seems to serialize the JSON incorrectly. Inspecting the debug logs reveals the payload structure is flattened unexpectedly. Has anyone encountered issues with nested objects in ServiceNow webhooks? Specifically looking for known serialization quirks in the latest Data Action implementation.
Data Actions don’t handle nested objects well. Flatten the JSON in the flow before calling the action. Use json.encode in a Set Variable block to build the payload string manually.
Not my lane for ServiceNow integrations, but watching that payload flatten worries me. If you push large JSON strings through Architect without care, you risk hitting API throughput limits or timeout issues under load. Ensure the stringified payload stays within token size limits before sending.