Filter (Zapier)

A filter is a step in a Zap that decides whether the workflow keeps going. It checks a condition against the data flowing through, and only if the rule passes do the later actions run. If the rule fails, the Zap stops at the filter and does nothing else. Filters do not consume a task.

How filters work

A filter evaluates one or more rules with and/or logic — "amount is greater than 100," "status equals paid," "email contains @company.com." You can layer multiple conditions:

• AND — every rule must be true for the Zap to continue.
• OR — any one rule passing is enough.

When the conditions are met, the Zap proceeds. When they aren't, the run halts and is marked as filtered, with no further steps and no task usage.

Filters vs paths

A filter is a single gate: continue or stop. A path is branching: it routes the run down different sets of actions depending on which conditions match. Use a filter when you only care about one outcome; use a path when the same trigger should do different things in different cases.

Why it matters

Filters are how you turn noise into signal. A Stripe trigger fires on every payment, but a filter can narrow it to large charges, a specific product, or paid-not-refunded status — so downstream actions (and the tasks they cost) only run on events that matter. Filtering early is also the main lever for keeping task usage, and your bill, under control.