Filter
Data NodeLet only the items that match a condition continue
Overview
The Filter Data node (in the Node Library's Flow Control tab) takes a list stored in a variable, keeps only the items that pass a condition, and saves the result in a new variable. Use it to skip empty rows or keep only high-priority records before you loop over them.
Filter before you loop
Point an "Apply to Each" loop at the filtered variable so the loop only runs for the items you care about. If a workflow contains the older Filter node (Field to Check / Condition / Compare Value), replace it with Filter Data or an If Condition — runs report that node as unsupported.
Parameters
Configuration options for this node
Source VariableText Input
Required
The name of the variable that holds the list to filter — for example the output variable of an Extract Data node.
Example:
recordsCondition (JS)Text Input
Required
A JavaScript condition checked against each item. Write it as an arrow function or as an expression using item (and index). Items for which it is true are kept.
Example:
item => item.Email !== ''Target VariableText Input
Required
The variable to store the filtered list in, so later steps can use it.
Example:
filteredItemsUsage Example
Only email rows that have an address
Skip any row where the email is blank
Source Variable:
rowsCondition (JS):
item => item.Email && item.Email.trim() !== ''Target Variable:
rowsWithEmailLoop over
rowsWithEmail: rows with an email are kept; blank ones are dropped.Best Practices
Tip: Filter early
Filter the list before the loop so you don't waste steps (or credits) processing items you'll throw away anyway.
Tip: Filter vs Switch
Filter Data simply keeps or drops items. If you need to send items down several different paths instead, use the Switch node.