Using Filter Nodes
Learn how filter nodes narrow your data using multi-condition AND/OR logic, type-aware operators, and how placing filters at different points in the flow affects downstream nodes.
Filter nodes let you narrow the data flowing through your document projection. They evaluate one or more conditions against each item and only pass through items that match. Filters can be placed before a loop to reduce the collection, or inside a loop to conditionally include content for each iteration.
Adding a Filter Node
Condition Structure
Each condition in a filter has three parts:
AND/OR Logic
When a filter has multiple conditions, you choose how they combine:
| Mode | Behaviour | Use Case |
|---|---|---|
| AND | All conditions must be true for an item to pass | Narrow results precisely - e.g. status is active AND category is billing |
| OR | At least one condition must be true for an item to pass | Broaden results - e.g. status is active OR status is pending |
Type-Aware Operators
The filter node inspects the data type of the selected field and offers only the operators that make sense for that type:
| Field Type | Available Operators |
|---|---|
| String | equals, not equals, contains, starts with, ends with, is empty, is not empty |
| Number / Integer | equals, not equals, greater than, less than, greater than or equal, less than or equal |
| Boolean | equals, not equals |
| Enum | equals, not equals, in, not in |
| Date | equals, before, after, between |
Filter Placement
Where you place a filter in the flow changes what it affects.
Before a Loop
Placing a filter before a loop reduces the collection that the loop iterates over. Only items matching the filter conditions enter the loop. This is the most common placement - for example, filtering entities to only those with a specific status before generating a page for each one.
Inside a Loop
Placing a filter inside a loop applies conditions to nested data within each iteration. For example, if you are looping over entities and want to show only certain properties of each entity, a filter inside the loop narrows the property list per iteration.
Downstream Reflection
When a filter is active, downstream nodes reflect the filtered data. Source field pills in output nodes show the filtered count rather than the total count. This gives you immediate feedback on how many items will pass through the filter without needing to preview the entire flow.