Stepthrough Start free

n8n If and Switch Nodes: Route Requests by Rules

A visual guide to n8n If and Switch nodes: split big jobs from small ones with one condition, then route by service with named outputs and a fallback.

  1. n8n. Let rules decide where each request goes. A service-request form, an email to the owner and a request log. If for yes or no, Switch for more than two roads.
    Slide 1 of 7
  2. Step 1. Send a test request first. Click Execute workflow and fill in the test form like a customer: a service and a budget of 2500. You need real data to route. Screenshot: An n8n service-request test form with a 2500 budget.
    Slide 2 of 7
  3. Step 2. If: Budget is greater than 1000. Drag Budget into value 1. n8n sees a number and switches the comparison to Number. Choose is greater than and type 1000 in value 2. Screenshot: n8n If node condition on Budget with the Number is greater than operator.
    Slide 3 of 7
  4. Step 3. Check which branch it took. Execute step shows True Branch (1 item), because 2500 is more than 1000. Each item takes one branch or the other, never both. True goes to the owner’s email, false to the log. Screenshot: If node output with the request on the True Branch.
    Slide 4 of 7
  5. Step 4. Switch: name outputs, keep a fallback. In Rules mode, each rule gets its own output: Repair, Emergency. Under Options, add Fallback Output and choose Extra Output, or items that match no rule are dropped. Screenshot: n8n Switch node with an Emergency rule and a Fallback output.
    Slide 5 of 7
  6. Step 5. Wire every road, then Publish. Repair goes on to the If, Emergency to the owner, Fallback to the log. If a number arrives as text, switch on Convert types where required. Screenshot: n8n canvas with form trigger, Switch and If nodes routing to Gmail and Google Sheets.
    Slide 6 of 7
  7. Build the routing free in a practice copy of n8n. Lesson: IF and Switch, route work by rules, about 10 minutes. Free at learn.ynteractive.com.
    Slide 7 of 7

Swipe or scroll sideways for all 7 slides. The whole guide is written out below.

The guide in text

A service-request form, an email to the owner and a request log. If for yes or no, Switch for more than two roads.

Step by step

  1. Send a test request first

    Click Execute workflow and fill in the test form like a customer: a service and a budget of 2500. You need real data to route.

  2. If: Budget is greater than 1000

    Drag Budget into value 1. n8n sees a number and switches the comparison to Number. Choose is greater than and type 1000 in value 2.

  3. Check which branch it took

    Execute step shows True Branch (1 item), because 2500 is more than 1000. Each item takes one branch or the other, never both. True goes to the owner’s email, false to the log.

  4. Switch: name outputs, keep a fallback

    In Rules mode, each rule gets its own output: Repair, Emergency. Under Options, add Fallback Output and choose Extra Output, or items that match no rule are dropped.

  5. Wire every road, then Publish

    Repair goes on to the If, Emergency to the owner, Fallback to the log. If a number arrives as text, switch on Convert types where required.

Businesses and people in the examples are made up (Harbor Point is a made-up business). The steps, screens and wording come from the free lesson and the Stepthrough glossary and prompt library.

Do it yourself, free

IF and Switch in n8n: Route Work by Rules. Send each request where it belongs. Use an If node to split big jobs from small ones, then a Switch with named outputs and a fallback to route by service. You do every step yourself in a practice copy of n8n, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts.

Start the free lesson

Or read the full step-by-step guide

Plain-English definitions, each with an example from a free lesson.

The full AI glossary

All free prompt templates

From the blog

All visual guides · All free tutorials