Trying to make sense of why the Data Action in my Architect flow is throwing a 400 Bad Request with the message Invalid JSON payload when attempting to map Zendesk ticket fields during our migration.
We are moving from Zendesk Support to Genesys Cloud CX, and the logic seems sound. In Zendesk, we used simple macro injections to pull custom fields, but here the Data Action expects a strict JSON structure. The error occurs specifically when the Zendesk API returns a ticket with a null value for a custom field that Genesys Cloud expects as a string.
Environment details:
- Genesys Cloud version:
v2024-10 - Region:
EU-West - Zendesk API:
v2 - Architect Flow: Simple linear flow with a Data Action node calling Zendesk REST API.
In Zendesk, null values were handled gracefully by the macro system. Here, it seems the Genesys Cloud Data Action fails entirely if the JSON structure doesn’t match the expected schema perfectly. Has anyone dealt with this specific schema validation issue? Is there a way to handle optional fields or provide default values within the Data Action configuration itself, or do we need to add a Transform node beforehand?