Conditional form logic, done as a graph

Why linear logic breaks past ~10 rules

Tally and Google Forms show conditions as a flat list under each question. Ten questions with three branches each and you're staring at 30 rows in a modal, hunting for the one that fires when "country = FR". Debugging a broken funnel means re-reading every row until the logic clicks.

Step 1 — Draw the flow first

Open a new flow and drop question nodes on the canvas. Zoom out once you have five or six — the shape of the funnel tells you which paths need conditions before you write a single rule.

Step 2 — Add branches with /if

Type /if on any question to attach a branch. Pick the field, the operator, and the target node — the edge draws itself. Skip logic is just a branch that points at the end node.

Step 3 — Compute values with /calc

Calculations are first-class. Use /calc to price a quote, score a lead, or roll up an assessment total — then branch on the result. No hidden fields, no glue scripts.

Step 4 — Disqualify early

For lead-gen and screener flows, disqualifiers belong at the top. Point the "No" branch at a short "thanks, we're not a fit" end node so the rest of the funnel stays clean and the completion rate for qualified users climbs.

Yectar graph logic vs Tally conditions vs Typeform logic jumps

• Visual first. The graph is the source of truth — no separate "logic view" to keep in sync.
• Calculations are native. Score, price, and tag inline — no hidden fields or Zapier math.
• Renders in any shape. The same logic graph powers the single-page, one-at-a-time, and embedded funnel renders.