Send people down the path their answers earned. Set a condition on a connection, and the form routes itself — no nested dropdowns, no shortcodes, no guesswork.
In most form plugins, conditional logic hides in a settings tab: a list of rules, referencing field IDs, describing behaviour you can’t see. It works until it doesn’t — and then nobody can say what the form actually does.
In QueryCue, a condition lives on the connection between two steps. You draw the line, you set the rule, and the branch is right there on the canvas: if the budget is over ten thousand, go here. A step can have several outgoing paths, each with its own condition, checked in the order you decide. The first one that fits wins.
Leave one connection without a condition and it becomes your fallback — the path for everyone the rules didn’t catch.
A condition can test any answer given so far — not just the question immediately before it. Route on the budget someone gave four steps ago.
Fifteen of them — equality, ranges, list membership, prefixes, emptiness. Text compares case-insensitively; numbers and dates compare as you’d expect.
Several conditions on one step? Give them a priority. QueryCue checks them in order and takes the first match — so the specific rule can beat the general one.
The schema validator flags loops that would never end, steps nothing can reach, and paths that dead-end before a thank-you screen — while you build, not after you publish.
Available on every connection, free edition included. Combining them with AND, OR and NOT — including nested groups, so you can express A and (B or C) — is a Pro feature.
Skip the questions a visitor’s answers already ruled out. Every branch you add makes the form shorter for someone.
Route the serious enquiry to a booking step and the browser to a guide — before either reaches your inbox.
The rules sit on the canvas, next to the steps they govern. Nobody has to reverse-engineer a settings panel.
Client-side logic can be bypassed — anyone can open the dev tools and post whatever they like. So when a submission arrives, QueryCue walks the flow again on your server, using the answers that were actually sent. If that path doesn’t end at a real success screen, the submission is rejected. And only the fields on the path the visitor genuinely travelled are kept — everything else is discarded before it’s ever stored. Fewer forged submissions, and no stray data you never asked for.
Branching is what the flow builder was made to draw — and what makes a multi-step form feel personal:
Simple conditions are included free. Draw a branch, publish, and watch the form adapt.