Does anyone know how to properly map a complex Zendesk macro sequence to a Genesys Cloud Script Node without triggering a 400 Bad Request? We are migrating our tier-1 support workflows from Zendesk to Genesys Cloud, and the translation is proving much harder than expected. In Zendesk, we relied on simple if-then macros to update ticket fields and send templated responses. I attempted to recreate this logic using the Set Variable and Email Action nodes in Architect, but the flow fails immediately upon execution.
The error log shows a validation failure on the email payload structure, specifically complaining about missing required fields that were optional in our legacy Zendesk templates. I have reviewed the Genesys Docs regarding the email schema, but the examples do not cover the dynamic field mapping we need from our legacy Zendesk CSV exports. The environment is EU-West-1, running the latest Architect version. As a beginner in GC admin config, I am struggling to understand why the variable binding fails when the data types appear correct. Any practical advice on structuring the JSON payload for the Email Action node to avoid this 400 error would be greatly appreciated. We need to stabilize this migration path before the cutover next week.