Looking for some advice on troubleshooting this persistent 422 Unprocessable Entity error when attempting to create a ServiceNow incident directly from a Genesys Cloud Architect flow using the Data Action integration.
The environment is running the latest patch level, and the ServiceNow REST API endpoint has been verified as functional via Postman with identical headers and payload structures. The issue appears isolated to the Genesys Cloud execution context. When the flow reaches the Data Action node configured for the ServiceNow integration, it fails immediately.
The response payload from the Data Action indicates a schema validation error on the caller_id field, despite the mapping explicitly pulling the contact_id from the active session context. I have cross-referenced the ServiceNow API documentation, which states that caller_id should accept a string or sys_id. The payload being sent looks correct:
{
“short_description”: “Test Incident from GC”,
“caller_id”: “{{contact_id}}”,
“description”: “Auto-created via Data Action”
}
The contact_id variable is populated and visible in the flow debug logs. Has anyone encountered a similar mismatch where Genesys Cloud sanitizes or transforms the variable type before serialization? I suspect the Data Action might be casting the string to an object type internally, causing the ServiceNow parser to reject it. Any insights on how to force a strict string cast within the Architect mapping would be appreciated.