Error: 400 Bad Request - Invalid Script Template Configuration
Hit a wall while trying to automate our Zendesk macro logic in Genesys Cloud Architect. The specific failure occurs when the flow attempts to trigger the script block using the standard API call. The response payload indicates a mismatch in the expected template structure.
{
"message": "Invalid script template configuration. Ensure the template ID matches an active script version.",
"status": 400
}
The setup involves mapping Zendesk’s text-based macros to Genesys Cloud’s structured script flows. I have verified that the Script ID corresponds to the correct version in the Admin console. The flow logic seems sound, passing the interaction ID correctly to the block. However, the system rejects the configuration immediately upon deployment.
Is there a specific formatting requirement for script templates that differ from the standard Zendesk macro syntax? We are migrating a high-volume support model, so understanding this discrepancy is critical. The documentation mentions template versions, but the error does not clarify if it is a versioning issue or a structural one. Any insights on how Zendesk macros translate to GC script blocks would be appreciated.