Multi-step Notion forms with logic: a step-by-step guide
Most Notion form tools stop at "one page, a few fields, dump it into a database." That works until you need to qualify leads, branch by answer, or gate a step on a specific condition. This guide walks through building a branched, multi-step lead-capture flow in Yectar that syncs straight to a Notion database — the kind of flow standard Notion form integrations can't produce.
What we're building
A three-step lead-capture flow: (1) collect name, email, and role; (2) branch on role — founders see a short qualifying question, everyone else sees a use-case question; (3) show a thank-you step and push the answers into a Notion "Leads" database.
Step 1 — Create the flow
In Yectar, hit /flowand start a new project. Every project is a directed graph of steps, so what you build here can render as a classic form, a multi-step form, a one-question-at-a-time experience, or a full funnel — same content, four shapes.
Step 2 — Add the first step
Type /short-text,/email, and/select to add three fields: name, email, and a role dropdown with options like "Founder", "Marketer", "Developer", "Other". Slash commands work the way they do in Notion — nothing to configure, no modal, just type.
Step 3 — Branch on role
Add a second step and open its logic panel. Set the condition to role == "Founder" and route matching submissions to a "founder qualifying" step (e.g. team size, current tooling). Add a fallback edge for everyone else that routes to a "use case" step. Because Yectar's runtime is a graph, you can keep adding branches without turning the flow into spaghetti — every path is explicit.
Step 4 — Thank-you and Notion sync
Add a thank-you step with a personalized message using {{name}}. In the flow's integrations, add the Notion connector, map fields to columns in your Leads database, and pick which step triggers the sync. Every submission — including the branched answers — flows into Notion as a new row, with the routing path recorded so you can filter founders separately from everyone else.
Why this beats a plain Notion form
- Real branching. Different answers for different people, not one flat form for everyone.
- Notion stays the CRM. Answers land in your existing database — no export, no glue code.
- Same flow, four shapes. Publish the same logic as a classic form, a multi-step form, a Typeform-style flow, or a funnel.
Try it on the founding-user plan
Yectar is launching soon. Join the waitlist for launch-day access, a founding badge, and first access to the API and MCP server.
Reserve free access