Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
The flow language is how instances share a design — Learn it in 5 minutes
About five minutes of reading
The designer is a view. The JSON is what you review and promote.
An action has a type, parameters, and transitions. Conditions can nest no more than five deep, with no more than 50 sub-conditions. Operators compare strings and numbers. A non-numeric comparison against GreaterThan returns false.
Action kinds are contact, participant, interaction, and flow control. Participant actions such as Play prompt need a participant. Some disconnect flows do not have one.
- Use the JSON to move a flow between a test instance and production.
- Do not hand-edit a 2,000-line export without a diff.
- Modules have their own JSON.
- The API still says Amazon Connect in places. The admin guide may say Connect Customer. The JSON types are what the API accepts.
Number on this page: Nesting 5. Maximum condition depth
Sources and go deeper
- Connect Customer Flow language - Amazon Connect AWS docs. last checked 2026-10
- Flow block definitions in the flow designer in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Interactive voice response - Wikipedia Wikipedia. last checked 2026-10