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

# Router Condition

> Route records to multiple named paths based on different conditions

Routes records to any number of output paths based on configurable conditions. Unlike Basic Condition (which only splits into True/False), Router lets you define multiple named branches - each with its own set of conditions.

## Configuration

| Setting   | Description                                                  |
| --------- | ------------------------------------------------------------ |
| **Paths** | One or more named output paths, each with its own conditions |

Each path specifies:

| Setting        | Description                                                                     |
| -------------- | ------------------------------------------------------------------------------- |
| **Name**       | Display name for this path (optional)                                           |
| **Logical**    | **AND** (all conditions must match - default) or **OR** (any condition matches) |
| **Conditions** | One or more conditions comparing a field to a static value                      |

## How It Works

<Steps>
  <Step title="Define paths">
    Add one or more output paths. Each path represents a different routing destination.
  </Step>

  <Step title="Configure conditions per path">
    For each path, define the conditions that determine which records are sent there.
  </Step>

  <Step title="Connect downstream nodes">
    Connect different processing nodes to each path output.
  </Step>
</Steps>

## Output

Each path creates a separate output. Records matching a path's conditions are sent to that output.

<Note>
  A record can match multiple paths and will be sent to **all** matching outputs. Records that don't match any path are not routed.
</Note>

## Example

Route contacts by region for different processing:

* **Path 1 "North America":** Region **equals** "NA"
* **Path 2 "Europe":** Region **equals** "EU"
* **Path 3 "Asia Pacific":** Region **equals** "APAC"

Each path connects to region-specific enrichment and notification workflows.

## Best Practices

* Name your paths clearly - they appear as labels on the workflow canvas
* Be aware that records can match multiple paths (this is useful for cross-cutting concerns)
* For simple two-way branching, [Basic Condition](/guide/nodes/condition/basic-condition-node) is simpler
* Conditions within each path are combined with the path's logic (AND/OR)

## Related Nodes

* **[Basic Condition](/guide/nodes/condition/basic-condition-node)** - simpler True/False branching for two-way decisions
* **[Field Comparison Condition](/guide/nodes/condition/field-comparison-condition-node)** - branches based on field-to-field comparison
* **[Simple Filter](/guide/nodes/filter/simple-filter-node)** - removes non-matching records instead of routing