Router
The Router node evaluates a set of rules against the incoming data and routes execution to a matching output path (called a pin). Each outgoing path has its own rule set; the first rule that matches determines which path is taken.
Use Router to implement conditional logic — branching the workflow based on field values, user properties, or other data.
Configuration
| Property | Type | Description |
|---|---|---|
dry_run | boolean | Run without executing task effects |
pass_input | boolean | Forward the incoming input to the matched branch |
filter_items | boolean | Filter out items that do not match any rule rather than raising an error |
error_on_no_match | boolean | Fail the task if the incoming data does not match any defined rule |
rules | array | The routing rules — see below |
Rules
Each entry in the rules array defines one output pin and the conditions that trigger it:
| Field | Description |
|---|---|
pin | The name of the output connection to route to when this rule matches (e.g. "default") |
mode | "all" — all conditions must match; "any" — at least one condition must match |
conditions | Array of condition objects defining the match criteria |
See also: Tasks overview
