Filters for Conditional Logic

By default, every time a trigger fires, the entire Zap runs. Every form submission, every email, every new row, they all execute all actions. But in reality, you do not always want that. You might only care about:

• Leads from specific countries;
• Emails from certain domains;
• Orders above a dollar threshold;
• Records with complete information.

Filters solve this by checking data against your conditions before allowing the Zap to continue. Think of it like a bouncer at a club, if you meet the criteria, you are in. If not, you do not get past that point.

When to Use Filters

Use a filter whenever you need to be selective about what data moves through your Zap.

Instead of trying to configure an overly specific trigger, which is often not possible, you set up a broad trigger that captures everything, then use filters to narrow it down to only the data you want to act on. This approach is more flexible, easier to maintain, and works with any app’s trigger options.

Adding a Filter to Your Zap

To add a filter to your Zap, insert a dedicated filtering step and define the conditions that control whether the workflow continues.

• Click the + button to add a new step;
• Search for Filter by Zapier;
• Select it, no external account is required since it is built into Zapier;
• Configure your conditions using the condition builder;
• Choose a Field from a previous step, select a Condition such as equals or contains, and enter the Value to compare against.

Filter Placement Strategy

Place filters as early as possible in your Zap:

# Trigger
  ↓
# Filter (check conditions) ← Early = efficient
  ↓
# Action 1
  ↓
# Action 2
  ↓
# Action 3

If the filter blocks data, none of the actions run. Zero tasks consumed.