Choosing a Flow Step

Choose the right Flow Step to route a run, split a list, or pause execution. Choose Conditions or Switch to route a run, and Filter to divide a list into matching and non-matching records.

At a glanceVerified in app · Oct 30, 2026

Use it to

Route a run across branches, divide a list into kept and discarded items, or pause and end execution

Find it

Tools → Flow (Conditions, Switch, Filter, Repeater, Subflow, Wait, Human Review, Stop and Error, Do Nothing)

Cost

Free for typed rules (0 Step credits) · AI Condition rules use Glow AI tokens

Output

Selected branch routes on Conditions and Switch · {{ N.kept }} and {{ N.discarded }} arrays on Filter

The three that route

They look alike in the panel because they share a rule builder. They answer three different questions.

	The question it answers	Works on	How many routes run
Conditions	Which of these are true?	the whole run	every one that matches
Switch	Which one of these is it?	the whole run	first match by default; optionally every match
Filter	Which items qualify?	a list or one record	only outputs with at least one item

Start with what you are holding

A list? That is Filter. It checks each item on its own and separates matches into KEPT and the rest into DISCARDED. Only nonempty outputs run their connected routes. Downstream Steps read {{ N.kept }} or {{ N.discarded }} explicitly, where N is the Filter Step number. Both fields are arrays, even when the input is one record.

One thing, and a path to choose? That is Conditions or Switch. Neither divides anything. They look at the run as a whole and decide which way it goes.

Then ask how many answers you want

Can more than one be true at once? Conditions evaluates each condition independently. “Is it over £10,000?” and “Is it in the UK?” can both be yes, and both routes run. Switch can also run multiple routes when Send to all matching branches is on.

Is it one of several? Use Switch. A ticket is a refund, a complaint or a question, not two of them. By default, cases are checked top to bottom and the first match wins, so ordering matters and a general case belongs at the bottom. Turn on Send to all matching branches under How matching works if you want every matching case to run.

What they share

All three are built from the same rule builder, so once you have written a rule in one you can write it in any of them:

• Pick the data, pick a type, pick an operator, give it a value. Six types cover most tests: Text, Number, Yes/no, Record, List, Date & Time.
• Rules in a group are joined with AND; groups are joined with OR. You choose which you are adding, not the combinator itself.
• Text is compared exactly unless you say otherwise. Active does not match active.
• A rule can be written in plain language instead, as an AI Condition, in Conditions and Filter. Switch is typed-only, whether it takes the first match or every match.

The full operator catalogue lives on the Conditions page and applies to all three.

The rest of the Flow group

The other Flow steps do not route on a rule. They change what happens next in some other way.

Step	What it does
Loops & Iteration	Repeats work: one step per item, or a body of several
Subflows	Runs another automation and waits for its answer
Wait	Pauses the run for a set time
Human Review	Pauses until a person approves or rejects
Stop and Error	Stops its branch and records a failure with your message
Do Nothing	Ends a branch tidily, so a route that should do nothing still completes

Verify it works

Run

Add Conditions, Switch, or Filter from Tools → Flow, configure a rule, and click Run step in Test & Debug.

You should see

The Output tab shows which branch matched or splits your list into kept and discarded arrays.

What’s Next?

• Route on several things at once with Conditions.
• Pick one of several with Switch.
• Split a list with Filter.