Skip to main content
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

SettingDescription
PathsOne or more named output paths, each with its own conditions
Each path specifies:
SettingDescription
NameDisplay name for this path (optional)
LogicalAND (all conditions must match — default) or OR (any condition matches)
ConditionsOne or more conditions comparing a field to a static value

​
How It Works

1

Define paths

Add one or more output paths. Each path represents a different routing destination.
2

Configure conditions per path

For each path, define the conditions that determine which records are sent there.
3

Connect downstream nodes

Connect different processing nodes to each path output.

​
Output

Each path creates a separate output. Records matching a path’s conditions are sent to that output.
A record can match multiple paths and will be sent to all matching outputs. Records that don’t match any path are not routed.

​
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 is simpler
  • Conditions within each path are combined with the path’s logic (AND/OR)