Does anyone understand why the Architect flow breaks when attempting to map Zendesk ticket priority levels to Genesys Cloud custom attributes via the Set Interaction Data block?
In the previous Zendesk environment, we used a simple numeric priority system (1-4) that drove routing logic. The goal is to replicate this by passing the priority value into the GC interaction attributes so downstream routing decisions can mirror the old tag-based behavior. However, the flow consistently fails at the specific block where the JSON payload is constructed.
The error returned is a 400 Bad Request with the message: Invalid attribute type for key 'zendesk_priority'. Expected STRING, got INTEGER. This is confusing because the Zendesk API returns integers, and I assumed GC would handle implicit conversion or that the attribute was created as a flexible type.
Environment details:
- Genesys Cloud Version: 2023-12-13
- Architect Version: 2023.12.1
- Source System: Zendesk Support API v2
- Attribute Type: Custom Interaction Attribute (String)
I have tried explicitly casting the integer to a string in the JSON structure, but the 400 persists. Is there a specific syntax required for the Set Interaction Data block when migrating integer-based metadata from Zendesk? The documentation mentions string coercion, but it seems to be failing in practice.