Filter
Filter is your lightweight, single-path gate. Configure one or more conditions; if they pass, the workflow proceeds. If not, the run ends gracefully at this step—no branching, no payload changes, just
Description
What it does: Filter evaluates one or more conditions and lets the workflow continue only if the conditions pass. Unlike Branch, it does not create multiple paths; it’s a single gate in your flow.
Use Filter when you need a yes/no checkpoint (e.g., “only proceed for paid users”, “skip if file isn’t PDF”, “run when score ≥ 0.8”). Use Branch when you need different actions for different outcomes. Add more rules with + And (all must pass) or group alternatives with + Or Group (any group that passes allows continuation).
Component settings
Tab "Config"
Only continue if
Build one or more rules. A rule consists of:
Field: pick an upstream value via @ (or select from the dropdown).
Choose condition
Choose an operator
(Text) Contains
(Text) Does not contain
(Text) Exactly matches
(Text) Does not exactly match
(Text) Is in
(Text) Is not in
(Text) Starts with
(Text) Does not start with
(Text) Ends with
(Text) Does not end with
(File format) Are
(Number) Equals
(Number) Greater than
(Number) Less than
(Date/time) Equal
(Date/time) After
(Date/time) Before
(Boolean) Is true
(Boolean) Is false
Exists
Does not exists
Is Null
Is Not Null
Value
Only available for Text, File format, Number and Date/time.
This allows you to enter a text, a number or a date/time.
Tab "Preview"
Use Preview to test your rule set against example inputs from recent runs.
True → the flow continues to the next node.
False → the run stops at Filter (no error; it is intentionally gated).
Advanced configurations
This component has no advanced configurations.
Use case
Filter - Allow flow run if "Field" contains value = 2
Only continue if = @ trigger.field
Condition = (Text) Contains
Value = 2
Set up at the "Filter" node
The result:
(1) When Field = 3 -> false
(2) When Field = 2 -> True
Last updated
Was this helpful?