Looking for advice on mapping complex Zendesk ticket fields to Genesys Cloud interaction attributes within an Architect flow. In Zendesk, we heavily relied on custom ticket fields for routing logic, which felt straightforward. Now, trying to replicate that in GC, I am hitting a wall with the “Get Interaction” action.
When the flow attempts to retrieve the interaction data, it returns a 400 Bad Request error with the message: “Invalid attribute path specified for interaction type.” We are using the Python SDK 10.5.0 to push initial data via the Digital Engagement API, mapping Zendesk custom fields to GC custom attributes. The data lands in the interaction, but the Architect flow cannot read it back correctly to trigger the specific routing rules.
Is there a specific delay or synchronization issue between the API push and the Architect’s ability to query these attributes? In Zendesk, this was instant. I suspect I might be missing a step in the attribute definition within the Architect workspace, but the documentation is vague on this specific migration path. Any insights on how to ensure these attributes are available immediately upon flow entry would be appreciated.