I can’t seem to figure out why the Architect flow fails when trying to map Zendesk ticket fields to Genesys Cloud Custom Attributes via the API. We are migrating our ticketing system and trying to push the priority and type fields from Zendesk into GC for reporting parity. The flow hangs on the “Set Custom Attribute” block and throws a 400 Bad Request with the message Invalid attribute value format.
The mapping logic looks correct in the flow editor, but the execution log shows a type mismatch. Here is the configuration snippet from the JSON export:
set_custom_attribute:
attribute_name: "zendesk_priority"
value_type: "string"
value_source: "{{trigger.zendesk_ticket.priority}}"
validation: "regex:^[0-9]+$"
In Zendesk, priority is an integer (1-4), but we are converting it to a string here. The trigger.zendesk_ticket.priority returns "high" in some cases and 1 in others, depending on the source. GC seems to choke on the mixed types despite the string conversion block preceding it.
Is there a specific way to sanitize this input before passing it to the Set Custom Attribute block? We want to maintain the exact Zendesk priority labels for our SLA reports. Any help with the data type handling in Architect would be appreciated.