Is it possible to dynamically assign Genesys Cloud skills based on Zendesk ticket tags within an Architect flow? We are migrating from Zendesk and need to replicate the old tag-based routing logic without manual intervention.
The current setup uses a Data Action to fetch ticket details, but the subsequent Skill assignment node throws a 400 Bad Request. The payload structure seems correct, yet the interaction fails to route properly.
Any working examples of this specific mapping pattern would be appreciated. We need to ensure the migration maintains our existing service level agreements.