Filter List

The Filter List node keeps only the items of a list that match your conditions. Each condition tests one field of every item, for example likes greater than 1000, or caption contains sale. Combine several conditions with AND or OR. Use Filter List to narrow a scraped or generated list before every remaining item runs through the next node. The node is free.

When to use it

• Keep only the scraped posts with enough likes before you rewrite them.
• Keep only the feed items published since the last scheduled run.
• Drop the items that miss a field, such as posts without a video.
• Make a batch smaller, and cheaper, before it runs through a paid node.

Quick start

Inputs and outputs

Filter List always works on the whole list connected to it. It runs once, never once per item, even on an Each connection. From a Generate Text - Any LLM node, the Items output hands over one item per ===NEXT=== block of the answer, and the Text output is one item, the whole answer.

Settings

Each condition

• Field — choose a field detected from the upstream data, (whole item) to test the whole item, or Custom path… to type a dot path such as author.name. ← Back to field list returns to the detected fields.
• Operator — equals, not equals, greater than, less than, greater or equal, less or equal, contains, does not contain, starts with, ends with, matches regex, exists or does not exist. exists and does not exist need no value.
• Value — the value to compare with. A toggle next to it switches between a typed value and a variable.

A value can also read another node. Wire that node to the Variables input, the lower input on the left, and write its label in curly braces as the value, such as {Keep id}. For example, a Generate Text - Any LLM node can answer with the id to keep. The whitespace around that node's output is ignored, so an answer that ends with a line break still equals the field.

Filter by date

Some fields hold a date or a time, such as created_at, published_at, timestamp, date, or any field that ends in _at or Date. When a condition uses such a field with greater than, less than, greater or equal or less or equal, the value becomes a date picker:

For example, published_at greater than Last N days with N set to 1 keeps the items published during the last day.

Other fields accept a typed value or one of these variables:

• {{now}} — the current time.
• {{trigger.last_triggered_at}} — the last time the workflow's trigger fired.
• {{last_N_hours:3}}, {{last_N_days:1}} and {{last_N_weeks:2}} — a time window back from now. Change the number to change the window.

Credits

Filter List is free.

Tips

• Filter before a batch. Every item you drop is one run of the next node that you do not pay for.
• Process only new items. Pair a Schedule Trigger with a Since last run condition, and each run handles only what arrived since the previous one.
• Look at the sample first. The field names in Upstream sample (first item) are the names your conditions must use.
• Pick instead of filter. To take one item or a slice by position, use Selector. To put the list in order, use Sort List.