English
Español
Português
Русский
العربية
See your form's logic like a map —
not a JSON tree
Every branch, page jump, and skip rule drawn as a diagram you can actually follow. The flow map turns invisible routing into something you can see, trace, and fix at a glance.
Branches, jumps, and skips — drawn out
Instead of scrolling a list of IF/THEN rules, you see the actual paths respondents take. Follow a Yes down one branch and a No down another, all on one canvas.
A sidebar that stays in sync with the canvas
Select a page on the map and the sidebar jumps to it — and back. The structure list and the visual canvas are always showing the same thing, so you never lose your place.
Catch dead ends before your respondents do
The map flags pages nothing leads to and paths that go nowhere, so a broken branch shows up while you build — not after someone gets stuck mid-form.
The map behind your logic
The flow map is how conditional logic and multi-page routing finally become visible.
Flow map — questions, answered
It is a visual view of your form logic. Instead of reading branching and page jumps as a list of rules, you see them as a diagram of connected pages and paths that respondents actually follow.
Conditional logic is where you write the rules; the flow map is where you see them. Every rule you set up appears on the map as a path, so the two work together.
Yes. The map flags pages that nothing routes to and branches that lead nowhere, so you can fix a dead end while building instead of after a respondent hits it.
It does. Selecting a page in the sidebar highlights it on the canvas and the other way around, so the list and the diagram always show the same structure.
The map is most useful on multi-page and branching forms, where routing gets complex. Simple single-page forms have little to map, but the view is always available.
Stop guessing where your logic goes
Build a form, add a branch, and watch the flow map draw the path for you.
Start building free
