Master Conditional Logic in n8n: If-Else, Branching, and Execution Order
Building a basic automation is a great start, but the real power of n8n lies in its ability to handle complex scenarios through conditional logic. In this lesson by GenAI Unplugged, we explore the intermediate concepts that turn linear workflows into “intelligent” systems capable of adapting to different data inputs [00:32].
1. Conditional Logic: If-Else vs. Filter Nodes
The foundation of any smart workflow is asking: “If this condition is true, do X; otherwise, do Y.”
- The If Node: This splits your workflow into two distinct paths: True and False. It’s perfect when you need to perform different actions for each scenario (e.g., if a lead is high-priority, notify a manager; if not, assign to a normal queue) [05:53].
- The Filter Node: Use this if you only care about the “True” path. Instead of routing to two branches, it simply stops the data that doesn’t match your criteria, making your canvas cleaner and more efficient [07:50].
2. Types of Branching in n8n
Branching allows your data to take multiple paths based on its characteristics:
- Conditional Branching: The standard 2-way split using the If node [01:43].
- Multi-Path Branching (Switch Node): When you have more than two categories (e.g., Order Status: Pending, Processing, Cancelled, or Refunded), the Switch node can output n different branches [08:44].
- Parallel Branching: Performing multiple actions from the same node simultaneously. For example, when an order is cancelled, you might want to send an email and a Slack notification at the same time [10:24].
3. Understanding Execution Order
To avoid errors, you must understand the order in which n8n processes nodes [03:17]:
- Sequence: One branch completes before the next one starts.
- Top to Bottom: Nodes positioned higher on the canvas execute first.
- Left to Right: If nodes are at the same height, the leftmost node executes first [11:02].
Why it matters: If Branch C depends on data generated in Branch A, but Branch C is higher on the canvas, your workflow will break because the data won’t be ready yet [03:24].
4. Bringing it Together: The Merge Node
Often, after splitting your data into branches to process it, you need to bring it back together to take a final action. The Merge node waits for all branches to finish, combines the data (often matching by a common field like Order ID), and outputs a single dataset for the next step [04:10].
Summary Table: Which Node to Use? [15:01]
| Node | Best Use Case |
| If Node | You need to do something for BOTH True and False results. |
| Filter Node | You only want to keep the “good” data and discard the rest. |
| Switch Node | You have 3+ categories of data that each need unique actions. |
| Merge Node | You need to combine data from two different sources/branches. |
By mastering these logic tools, you ensure your automations are not only powerful but also resilient to the many “what if” scenarios of real-world business data.
Watch the full deep-dive here: Master Conditional Logic in n8n
