Does anyone know if there is a direct mapping for Zendesk ticket tags within the Genesys Cloud BYOC Edge configuration? The migration script is failing because the Edge instance does not recognize the custom metadata fields we use for ticket routing rules in Zendesk. We are seeing a 400 Bad Request error when trying to push these tag-based attributes through the /api/v2/architect/flows endpoint. The documentation mentions custom attributes but does not clarify if they support the dynamic tagging logic we rely on for our current Zendesk workflows. We need to replicate the exact same routing behavior without losing the historical tag data associated with each interaction. Is there a workaround to inject these tags into the Genesys Cloud interaction object before it hits the flow logic?
Does anyone know if there is a direct mapping for Zendesk ticket tags within the Genesys Cloud BYOC Edge configuration?
This is caused by the Edge API rejecting unmapped custom metadata. Use the CLI to define the schema first, then map the tags to customerAttributes in the flow HCL.