Does anyone know how to handle the Error 400: Invalid Input Type when trying to replicate a Zendesk Dynamic Voice Menu in Genesys Cloud Architect?
We are currently migrating a complex IVR structure from Zendesk Voice to Genesys Cloud. In Zendesk, we used dynamic menu options that updated based on real-time ticket queue depths. We are trying to build an equivalent flow in Genesys Cloud using the “Play Prompt” and “Get Input” blocks, but we are hitting a wall.
The specific issue occurs when we try to map the dynamic options list from a previous data block (fetching queue stats via REST API) into the “Options” field of the “Get Input” block. Genesys Cloud seems to expect a static list of choices defined in the block configuration, rather than a dynamic variable reference. When we attempt to deploy the flow with a variable reference like {{flow.QueueOptions}}, the validation fails with the 400 error mentioned above.
Here is the context:
- Source System: Zendesk Voice (Dynamic Menus enabled)
- Target System: Genesys Cloud (Architect v2.1.0)
- Error:
Error 400: Invalid Input Type - Options must be a static array of strings - Environment: Genesys Cloud US-1, Standard Edition
I have checked the documentation for “Dynamic Choices” in Architect, but it mostly covers using variables for prompt text, not the selectable options themselves. Is there a workaround using a “Run Script” block or a specific API call to dynamically update the IVR options? Or are we forced to use a static menu and route based on post-input logic?
This is a critical blocker for our migration timeline. The client insists on having the same dynamic experience as Zendesk. Any advice on how to architect this properly in Genesys Cloud would be hugely appreciated. I am still learning the nuances of the Architect canvas compared to the simpler Zendesk builder, so I might be missing a basic configuration step.