Skip to Content
πŸ›  BuildπŸ›  Action StepsChoosing a Flow Step

Choosing a Flow Step

The Flow group holds the steps that decide what happens next rather than doing outside work. Three of them route, and picking between those three is the choice people get wrong most often.

The three that route

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

The question it answersWorks onHow many routes run
ConditionsWhich of these are true?the whole runevery one that matches
SwitchWhich one of these is it?the whole runthe first that matches, only
FilterWhich items qualify?a list or one recordboth, each with its own items

Start with what you are holding

A list? That is Filter. It checks each item on its own and sends the matching ones down KEPT, the rest down DISCARDED. Both routes carry on with their share, so you can email the ones that passed and log the ones that did not.

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? Use Conditions. β€œIs it over Β£10,000?” and β€œIs it in the UK?” can both be yes, and both routes run. That is the thing a true/false switch cannot do, and the reason Conditions exists.

Is it one of several? Use Switch. A ticket is a refund, a complaint or a question β€” not two of them. Cases are checked top to bottom and the first match wins, so ordering matters and a general case belongs at the bottom.

A single record through a Filter is a useful gate. β€œOnly carry on if this order is over Β£500” works as a one-item Filter, and the difference from a Conditions step is what travels: the Filter sends the record itself down the route, where Conditions sends only the decision.

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: String, Number, Boolean, Object, Array, 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, deliberately: it picks one route out of several and stops, so the answer decides where the whole run goes. That is the place you want a comparison rather than a judgement.

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.

StepWhat it does
Loops & IterationRepeats work β€” one step per item, or a body of several
SubflowsRuns another workflow and waits for its answer
WaitPauses the run for a set time
Human ReviewPauses until a person approves or rejects
Stop and ErrorEnds the run deliberately, with a message you write
Do NothingEnds a branch tidily, so a route that should do nothing still completes

What’s Next?