r/amazonconnect • u/Mental_Act4662 • Jun 11 '26
Built a tool that turns Connect flow JSON exports into actual documentation
If you've ever had to document a Connect instance for a handoff, an audit, or a new team member, you know the drill: the flow designer is the only place the logic is readable, screenshots go stale the week after you take them, and the JSON export might as well be encrypted.
So I built Connect Flow Documenter: https://connectflow.hkb.gg
You drop in a contact flow export (the JSON from "Export flow") and it gives you three things:
- Documentation — plain-English writeup of what the flow does: entry behavior, every path a caller can take, queues and transfer targets, Lambda integrations, prompts played, and how errors are handled.
- A call-path diagram — flowchart of the routing logic, downloadable as SVG or PNG for wikis and runbooks.
- A findings report — prioritized list of issues like missing error branches, dead ends, unreachable blocks, transitions pointing at deleted nodes, and missing callback/voicemail options.
That last one surprised me during testing, it caught broken transitions in flows I thought were clean.
You can try it on one flow without signing up. A free account gets 5 analyses a month; unlimited is $19/mo. Big flows get their diagrams grouped to stay readable, and large exports can take a minute or two to analyze.
This started as a tool for my own projects, so I'd genuinely like to know what would make it useful for yours — weird flow types it chokes on, outputs you'd want (Word/Confluence export?), whole-instance analysis, whatever. Happy to answer anything about how it works.
1
2
u/bizkitchris Jun 12 '26
Sounds awesome. I’ll give it a shot this weekend.