Conditional Logic

Conditional logic is the mechanism that lets software behave differently depending on the value of some piece of data — the no-code equivalent of an `if/else` statement, expressed visually rather than in text-based syntax. It's one of the most fundamental building blocks across every no-code category: form builders use it to show or hide questions (skip logic), automation platforms use it to branch a workflow down different paths (a Zapier "Filter" or "Path," a Make "Router"), and database apps use it in formula fields to compute different outputs based on record data. Why it matters: conditional logic is the difference between a tool that just moves data around and one that actually encodes decision-making — it's what elevates "when a form is submitted, send an email" (a simple linear automation with no logic at all) into "when a form is submitted, if the requested budget exceeds $10,000, route to a manager for approval; otherwise, auto-approve and notify finance" (a workflow that mirrors genuine business decision-making). Nearly every non-trivial automation or app a citizen developer builds requires at least one conditional branch, making it arguably the single most important no-code skill to master beyond basic trigger/action chaining. How it works: most platforms express conditional logic through one of two interaction patterns. The first is a filter/gate: a single condition that either lets the workflow continue or stops it entirely (Zapier's "Filter by Zapier" step — "only continue if Deal Stage = Closed Won"). The second is a branch/router: a decision point that sends execution down one of multiple possible paths depending on which condition matches (Make's "Router" module, Bubble's "Terminate this workflow if... / Only when..." conditions on each step). Worked example — a Make scenario using a Router to handle three different lead-quality tiers from a single trigger: Trigger: "New Lead Form Submission." Router Path A (condition: `lead.company_size >= 500`): create a high-priority Salesforce opportunity and notify an Enterprise AE directly via Slack DM. Router Path B (condition: `lead.company_size >= 50 AND lead.company_size < 500`): add to a mid-market nurture sequence in HubSpot and create a lower-priority CRM task. Router Path C (fallback, no condition matched — catches everything else): add to a general newsletter list only, no sales follow-up. This single automation encodes an entire lead-qualification policy — three different business responses to the same trigger event, based purely on conditional evaluation of the incoming data — without a developer writing a single `switch` statement.