Two node types check a condition and send the run one way or the other: condition and branch. They work identically — use whichever reads better in your diagram.
The comparisons available
- equals, does not equal — text comparison.
- greater than, less than, and their "or equal" forms — number comparison.
- is empty, is not empty — whether the field has anything in it.
- contains — whether the text appears anywhere in the field.
A condition can require all of a set of tests, or any of them.
Two traps worth knowing
- "Equals" compares text. Comparing a number field with equals compares it as written, so 5 and 5.0 are not the same. Use the number comparisons when you mean numbers.
- An unconfigured condition passes everything. A condition node you dragged on and never configured does not block the run — it lets everything through the true side. Configure every condition you add.
Both sides need connecting
A condition has a true output and a false output. If nothing is connected to the side a run takes, the run simply stops there. That is often what you want — but if a workflow appears to do nothing for certain records, an unconnected false output is the usual reason.