nodes / builtin / flow
Filter
Accept items matching the conditions
Keep only the items that match your conditions and drop the rest.
What it does
Section titled “What it does”Filter checks its Conditions once for every item that arrives. Items that match leave through the Kept port, unchanged. Items that don’t match are dropped: they go nowhere, and the steps after Filter never see them.
Conditions work like the ones in If: each compares a value (usually an expression such as {{ $input.price }}) with another value, using an operator for the type you pick (String, Number, Date-Time, Boolean, Array or Object). Link several conditions with AND or OR. In steps saved before 0.9 they are read from top to bottom, one after the other, with no grouping: A AND B OR C means “(A and B), or C”. New steps use groups (see below).
Conditions in AWFlow 0.9
Section titled “Conditions in AWFlow 0.9”New Filter steps (version 2) build conditions as cards, one rule per card:
- Match all or Match any applies to a whole group of rules, and Add group nests a group inside another, so “A and (B or C)” is easy to read. AND / OR between cards is shown for you.
- Operators have plain names, grouped by type: is equal to, contains, matches pattern (advanced), length is… and so on. Lists and objects are compared by their content.
- Options › Type check: Loose converts values when it can (with a warning), Strict fails the step and names the rule and the item when a value has the wrong type. Ignore case compares texts without caring about capitals (an Aa ignored chip shows it).
- An empty date or number never counts as a date or as 0: the rule is false and the run log says why. An invalid pattern or date fails with “Condition N: …”.
Steps saved before 0.9 keep their rows, read top to bottom with each row’s own AND/OR. Update in the step’s header converts them to groups with exactly the same meaning. XOR means “exactly one of the two” (it used to behave like OR); it is only offered on rows that already use it.
When to use it
Section titled “When to use it”- Keep only the products under a price before sending an alert.
- Remove empty rows from a CSV before saving them.
- Keep only the links that point to a given domain.
To send the non-matching items somewhere else instead of dropping them, use If. To keep the first few items whatever their content, use Limit.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Conditions (required) | Conditions | The conditions to evaluate. |
Write the value to test as an expression on the current item, for example {{ $input.status }} Is Equal To active.
Outputs
Section titled “Outputs”-
Kept
Each output item has these fields:
| Field | Type | What it holds |
|---|---|---|
| result | True/false | Whether the conditions held |
| inData | Any | The incoming data, unchanged |
{ "result": true, "inData": null}The next node receives the kept items themselves, exactly as they arrived, so you keep using the same expressions ({{ $input.price }}) after the Filter. If no item matches, nothing leaves the node.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”Keep only the PDF links of a page:
- Get All Link with Output field name
linksreads the links of the open page. - Split Out with Field To Split Out
linksmakes one item per link. - Filter with the condition
{{ $input.links }}(String) Ends With.pdf. - Slack posts
{{ $input.links }}for every kept link.
Common issues
Section titled “Common issues”-
Nothing runs after the Filter. No item matched. Open the run and check the values the condition compared: a price read from a page is often text such as
"49.90 €", which a Number comparison can’t match. Clean it first with Edit Fields or Regex. -
Items you expected to drop still pass. Check the AND / OR links. Because conditions are read top to bottom without grouping, one OR near the end can let everything through.
-
Every item is dropped when comparing text. Text comparisons are exact; check for extra spaces or a different capitalisation in the incoming value.
-
The Filter fails before it starts. A Filter needs at least one condition: with none, it fails with a clear message instead of keeping or dropping everything.
Related nodes
Section titled “Related nodes”- If: route non-matching items to a second branch instead of dropping them.
- Switch: send items to one of several branches.
- Remove Duplicates: drop repeated items.
- Limit: keep only the first items.