Browse the docs
Preparation node

Route

Send each row down one of several named branches, where the first matching rule wins. For a single yes/no condition, use Filter.

Category
Preparation
Also known as
router, split, conditional split, partition, case, switch, branch, multi-way, segregate, fan out, region, tenant

What it does

Sends each row down ONE of several named branches. Rules are tried in order and the first one that matches wins, so a row that matches two rules leaves on the higher one; anything matching no rule leaves on Unmatched. Together the anchors are the whole input: nothing is dropped and nothing is duplicated. Build each rule with the picker, or write a SQL expression.

Inputs and outputs

InputsOne input.
OutputsOne output per rule (2 to 10 rules), each named after its rule, then Unmatched for rows no rule caught.

When to use it

  • Split one feed into several destinations: a table, a file or a mailbox per region, tenant or product line
  • Triage by severity, where the rules deliberately overlap and the order is what decides which one applies
  • Anywhere you would otherwise chain Filters: one Route replaces four of them and reads the data once

Examples

Split by region

West · region is West

Basic mode: column, operator, value, the same picker Filter uses. Add a rule per region; the rest fall to Unmatched.

Order decides, on purpose

Fraud · amount > 10000 AND country <> home_country

With Treasury and Rates below it, a row matching all three leaves on Fraud only. That is what first-match-wins means.

Catch what you did not expect

Unmatched

Wire it to a table or a Send Email node and a value nobody planned for stops being invisible.

Tips

  • The run’s Messages tab lists how many rows took each branch, Unmatched included, so you can see what fell through without wiring anything up.
  • Rules are tried top to bottom. Use the arrows to reorder them; the canvas edges follow their rule, so nothing is silently re-pointed.
  • A freshly dropped Route starts with two empty rules and is flagged in the builder until each rule has a column and, for most comparisons, a value.
  • A branch name labels its anchor on the canvas and names it in the routing tally. Two rules cannot share a name.
  • Dates are written YYYY-MM-DD (and date-times YYYY-MM-DD HH:MM:SS) everywhere in Trinium.
  • One condition? Use Filter. It is the simpler node, and a Route needs at least two rules.