13 · data
Keep or drop items that match conditions — without forking the canvas.
When to use it
You have many items on one pin and only some should continue. Prefer IF when you still need an else path with different work.
Writeup
Keep or drop items that match conditions — without forking the canvas. You have many items on one pin and only some should continue. Prefer IF when you still need an else path with different work.
Step by step — how to wire it
01
Place after a list
After HTTP that returns many rows, or Split Out fields.
02
Set conditions
e.g. {{$json.email}} is not empty.
03
Continue the happy path
Filter → Gmail / Sheets only for survivors.
04
Log drops if needed
If you must audit rejects, use IF instead so the false pin can Sheets-append.
How it functions
Pass / remove
Items that fail the condition are removed from the stream (no false branch).
Chainable
Filter → Filter is fine for progressive constraints.
Used for
Used for 1
Dropping empty emails before Gmail
Used for 2
Keeping only failed rows from a list
Used for 3
Thinning noisy webhook bursts
Tips
Filter is quieter than IF — no false pin means easier canvases, harder audits.
Combine with Limit when testing against huge payloads.