I’m completely stumped as to why the POST /api/v2/scripts endpoint returns a 400 Bad Request when attempting to map Zendesk macro actions to Genesys Cloud script steps. The migration tool is failing specifically on the “Send Email” macro action, which we are trying to convert into a Genesys script node for agent assistance.
The error response indicates: "code": "invalid_body", "message": "The property 'actions' is required and must contain a valid list of script actions.". We are using the latest version of the Genesys Cloud API (v2) and have verified that the JSON payload conforms to the schema outlined in the Genesys Docs.
In Zendesk, a macro is a simple list of field updates and notifications. In Genesys, scripts are flow-based with specific node types. We are attempting to map the Zendesk macro’s “Send Email” action to a Genesys “Send Message” node within the script. The payload structure we are sending looks like this:
{
"name": "Migrated Macro Script",
"steps": [
{
"type": "send_message",
"actions": [
{
"template": "email_template_id_from_zendesk",
"to": "{{contact.email}}"
}
]
}
]
}
However, the API rejects this, stating that the actions array is invalid. We have tried using send_email instead of send_message, but that results in a different 400 error: "Unknown action type: send_email".
Is there a specific mapping required for Zendesk email macros to Genesys script actions? We are migrating from Zendesk Sunshine Conversations to Genesys Cloud and need a reliable way to automate agent scripts based on previous macro usage. Any insights on the correct node type or payload structure for this migration step would be greatly appreciated. We are currently stuck on this step and cannot proceed with the bulk migration of our agent workflows.