> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# If/Else Branch

> Route contacts down different paths by evaluating multiple conditions sequentially.

The If/Else Branch node evaluates multiple conditions in sequence and routes each contact to the first matching path.

Each condition is built using the [Unified Query Engine](/product-docs/unified-query-engine/overview), giving you access to contact fields, company fields, engagement data, audience membership, and more.

## Configuration

| Setting                | Description                                                                                               |
| ---------------------- | --------------------------------------------------------------------------------------------------------- |
| **If condition**       | The first condition to evaluate. If it matches, the contact follows this path.                            |
| **Else if conditions** | Additional conditions evaluated in order. A contact follows the first one that matches.                   |
| **All others**         | A default catch-all path that is always present. Contacts who don't match any condition follow this path. |

### Adding branches

Click **Add branch** to add a new Else if condition. There is no limit to the number of branches you can add.

### Building conditions

Each branch uses the same condition builder as the [True/False Branch](/product-docs/workflows/nodes/true-false-branch) node. You can combine multiple conditions within a single branch using AND/OR logic and nested groups. For details on available operators and field types, see the [Unified Query Engine overview](/product-docs/unified-query-engine/overview).

## Behavior

* Conditions are evaluated **top to bottom** (left to right visually on the canvas), starting with the If condition.
* As soon as a condition matches, the contact follows that path. **Remaining conditions are not evaluated.**
* If no condition matches, the contact follows the **All others** path.
* Each contact follows exactly **one path**.
* Contacts are evaluated using the most current data available at the moment they reach the node.

## Example

An If/Else Branch that routes contacts by name:

| Branch         | Condition               | Result                      |
| -------------- | ----------------------- | --------------------------- |
| If             | `First Name = Alice`    | Follows the If path         |
| Else if        | `First Name = Bob`      | Follows the Else if path    |
| **All others** | (no conditions matched) | Follows the All others path |

A contact named Alice matches the first condition and follows the If path. The remaining conditions are skipped. A contact named Carol doesn't match any condition and follows the All others path.

## When to use If/Else Branch vs. other branch types

| Node                                                                 | Best for                                                                  |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **If/Else Branch**                                                   | Multiple conditions with different logic per path, evaluated sequentially |
| [True/False Branch](/product-docs/workflows/nodes/true-false-branch) | A single yes-or-no decision point                                         |
| [Field Branch](/product-docs/workflows/nodes/field-branch)           | Routing by exact values of a single field                                 |

## Use cases

* **Engagement-tiered nurture** — route contacts into high, medium, and low engagement paths based on email activity thresholds
* **Lead scoring tiers** — send hot leads to sales, warm leads to a nurture sequence, and cold leads to a re-engagement flow
* **Multi-region routing** — direct contacts to region-specific messaging based on country or locale
* **Lifecycle-based onboarding** — deliver different onboarding content for trial users, new customers, and returning customers
* **Funnel stage actions** — trigger different follow-ups depending on how far a contact progressed through a signup or demo request flow