Quick question, has anyone seen this weird error? with the Web Messaging channel during our Zendesk-to-GC cutover. When trying to map Zendesk’s ‘Status’ field to Genesys Interaction Attributes via a Data Action, the flow throws a 400 Bad Request with error code INVALID_ATTRIBUTE_TYPE. The documentation at Genesys Docs suggests string mapping works, but our Architect flow fails immediately. In Zendesk, this was just a simple dropdown sync. Why is GC rejecting the string payload here?
The documentation actually says…
- Map the Zendesk status to a numeric enum value first, as Genesys Interaction Attributes for channel-specific fields often reject raw strings.
- Verify the target attribute in Architect is set to
IntegerorEnumrather thanStringto avoid theINVALID_ATTRIBUTE_TYPEerror.