Architect Data Action Webhook Failing with 422 Unprocessable Entity for ServiceNow Incident Creation

I’m curious as to why the Genesys Cloud Architect Data Action webhook is returning a 422 Unprocessable Entity error when attempting to create a new incident in ServiceNow via REST API? The environment is Genesys Cloud v24.2 and ServiceNow Washington DC Patch 4. The integration works perfectly for standard voice channel triggers, but fails specifically when triggered from a Digital Channel (Webchat) context.

The issue appears to be related to how the webhook payload handles the contact_id field when passed from the digital channel session. The ServiceNow REST API expects a specific format for the caller_id or contact field, but the 422 response suggests the JSON structure being sent is invalid or missing a required schema property. I have verified the ServiceNow table schema and the API endpoint is correct. The error occurs immediately upon the webhook execution in the Architect flow.

Here is the JSON payload being constructed in the Data Action step:

{
 "u_contact_name": "${contact.name}",
 "u_contact_email": "${contact.email}",
 "u_genesys_ticket_id": "${interaction.id}",
 "u_channel_type": "${routing.channel.type}",
 "description": "${transcript.summary}",
 "short_description": "Webchat Issue: ${routing.queue.name}",
 "caller_id": "${contact.id}"
}

The contact.id field is populated correctly in the Architect debug view. However, ServiceNow logs indicate that the caller_id field is receiving an unexpected data type or format. I suspect there might be a type casting issue between the Genesys Cloud string representation of the ID and the ServiceNow GlideRecord reference field.

I have checked the ServiceNow API documentation for the incident table, and the caller_id field accepts a sys_id string. The webhook timeout is set to 30 seconds, and retries are disabled for this test. The error message from ServiceNow is generic: “Invalid field value for caller_id”.

Has anyone encountered similar issues with digital channel contact IDs being passed to ServiceNow via webhooks? Is there a specific formatting requirement or additional transformation step needed in the Architect flow to ensure the contact.id is correctly interpreted by the ServiceNow REST API? Any insights into the data type expectations for this field would be appreciated.

TL;DR: Mismatched schema.
This looks like a classic payload validation failure where the Digital Channel context injects extra metadata that ServiceNow’s strict incident schema rejects. Verify the Data Action mapper is stripping non-essential fields before the POST request hits the ServiceNow endpoint.

have you tried stripping the payload in a script node before the data action? digital channels inject extra metadata that service now rejects. my jmeter tests show this breaks concurrency. map only required fields like short_description to avoid 422 errors.