Outbound campaign completion triggers a ServiceNow Data Action that returns a 422 Unprocessable Entity. The payload matches the schema validated in Postman, yet Architect fails to parse the nested contact attributes. Has anyone hit this serialization bug with recent GC updates?
A 422 error usually means the payload structure is valid, but the semantic logic fails. For ServiceNow integrations, this often hits when nested contact attributes contain null values or unexpected data types that the target table rejects. Even if Postman works, Architect might be serializing empty fields differently during high-volume outbound campaigns.
Check the specific field mapping in your Data Action. If you are passing a contact_id or phone_number that is optional in Genesys Cloud but mandatory in ServiceNow, the integration will fail. Try adding a conditional transformation in Architect to ensure these fields are either populated with a default value or stripped entirely if empty. Also, verify that the ServiceNow table allows the specific user context of the integration runtime. Sometimes the issue isn’t the data itself, but the permission set of the integration user trying to write to that specific record.
While semantic validation is a common culprit, verify the JSON structure against ServiceNow’s strict typing. Architect sometimes serializes empty strings as nulls, which ServiceNow rejects if the field expects a string. Force explicit string casting in the Data Action mapping to prevent type mismatches. Also, check if the endpoint supports batch processing, as single-record payloads might behave differently under load.