Does anyone know how to properly map Zendesk ticket macros to the Genesys Cloud Scripting API during our migration? We are trying to replicate a complex Zendesk macro that updates the ticket status and adds a private comment based on specific tags. In Zendesk, this is a single click action, but in Genesys, we are attempting to use the scripting API to trigger these updates via an Architect flow. The issue is that the Genesys API seems to require separate calls for status updates and comment additions, which breaks the atomic nature of the original macro. We are getting a 400 Bad Request error when trying to pass the Zendesk-specific tag values into the Genesys interaction context. The error message states “Invalid field value for interactionType”. We have verified that the integration is active and the API keys are correct. The problem seems to be with the payload structure expected by the Genesys scripting engine compared to the Zendesk API. Does anyone know the correct JSON payload structure for the Genesys Scripting API to update a Zendesk ticket status and add a comment in a single atomic operation?