Quick question about mapping Zendesk Macros to Genesys Cloud Agent Scripts via the Script API. We are currently in the final stages of migrating our digital channel workflows from Zendesk to Genesys Cloud EU1. The goal is to replicate the automated macro execution logic that triggers specific actions based on ticket tags. When attempting to create a new script using the POST /api/v2/scripts endpoint with the payload derived from our Zendesk macro definitions, we consistently receive a 400 Bad Request error. The response body indicates a validation failure on the items array, specifically stating that stepType must be one of the allowed values. We are trying to map the Zendesk “Change Status” macro action to a GC script step, but we are unsure if the SCRIPT_STEP_TYPE enum in the GC API supports a direct equivalent for updating interaction attributes in the same way Zendesk updates ticket fields. Our current payload includes a stepType of FIELD_UPDATE, which seems to be rejected. Is there a specific configuration or a different stepType we should be using to achieve this attribute update within a script? We have verified that the user making the API call has the script:view and script:add permissions, so this does not appear to be an authorization issue like the 403 errors we encountered with the Identity API earlier this week. The environment details are as follows: Genesys Cloud EU1, API Version v2, and we are using the Python SDK version 12.0.0 for the migration scripts. Any insights on how to correctly structure the script item to mimic the Zendesk macro behavior would be greatly appreciated. We want to ensure that the transition for our agents is seamless and that the digital channel migration does not result in a loss of automation capabilities. The current blockage is preventing us from completing the user acceptance testing for the script module.