Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 36 ยท Filters, Paths and Formatting

Filters: Only Continue If

Use filter steps to stop Zap runs unless conditions are met: operators, AND/OR groups, empty checks, case sensitivity, gotchas, and a runnable filter evaluator stand-in.

Not every event should trigger work. A form submission might be spam, a deal update might not be a stage change, an email might not match your rules. A filter step sits in the middle of a Zap and says: only continue if these conditions are true. If they are not, the run ends there, quietly and on purpose.

Zapier cannot run on this site. Filter menus are described in words; operator names can vary slightly by version. The Python blocks are labelled stand-ins that implement the same logic.

How a filter behaves

A filter step has one or more rules, each comparing a field (chosen with the data picker) with a value using an operator. If the whole condition is true, the Zap continues. If false, the run stops and Zap History shows it as stopped or filtered. Filters are generally not counted as tasks (verify current rules in plans, tasks and limits), and stopping early prevents later actions from consuming tasks.

flowchart LR
  T["Trigger"] --> F{"Filter: amount greater than 100 AND country is DE"}
  F -->|"true"| A["Actions run"]
  F -->|"false"| X["Run stops (not an error)"]

A filter is a gate. A stopped run is a normal, successful outcome of the Zap design.

Operators you will use

Kind Operators (typical wording)
Text contains, does not contain, exactly matches, does not exactly match, starts with, ends with
Presence exists, does not exist
Numbers greater than, less than, equals
Dates is after, is before
Booleans is true, is false

"Exists" checks that the field has a value at all; it is the right tool to protect against empty fields. Be aware that "does not exist" and "is empty" differ slightly among versions; read the operator's help.

Combining conditions

You can add several rules and combine them:

  • AND: all rules in the group must be true.
  • OR: at least one rule (from a separate group) must be true.

A common pattern: (country is DE AND amount > 100) OR customer is VIP. Zapier lets you build "AND" groups and add an "OR" alternative. Keep conditions readable; if a filter needs a dozen rules, consider Paths or a lookup table instead.

Case, spaces and types

Common filter surprises:

  • Case: "Contains" is usually case-insensitive in Zapier, while "exactly matches" may be case-sensitive. Test it.
  • Whitespace: "Ada " is not "Ada". Trim text first with Formatter.
  • Types: text "100" versus number 100. Comparing numbers as text gives wrong results ("9" is greater than "10" alphabetically). Use numeric operators or convert first.
  • Empty fields: a missing value may be null or an empty string. Use an explicit exists check.
  • Dates: compare dates only after they share a format and time zone (dates).

A filter evaluator: a stand-in

The stand-in below implements a small filter language with AND groups and an OR between them. Edit the record and the rules to see the results.

Python Stand-in: evaluating filter rules

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The last record has no amount; the numeric rule simply fails, so the run stops. In a real filter you would add an "exists" rule to make the intent explicit.

The text-versus-number trap

Here is the bug that bites everyone once.

Python Stand-in: comparing text and numbers

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

If a filter says "amount greater than 100" and your amount arrives as text, make sure the operator or a Formatter step treats it as a number.

Where to place filters

  • As early as possible: stops irrelevant work and saves tasks.
  • After lookups when the condition needs searched data (such as the customer's plan).
  • Before irreversible actions such as emails to customers.
  • Between two Zaps: a "gate" filter at the top of a Zap, rather than at its end.

You can also filter inside a path (each branch has its own rule); see Paths.

Filter or Path?

Need Use
"Do these steps only when X" Filter
"If X do A, else if Y do B, else C" Paths
Many conditions mapped to values Lookup table (lookups)

Debugging a filter

If the Zap does not continue, open the run, find the filter step and read what values it compared. Check the real data, not the editor's sample. The usual culprits: extra spaces, different capitalization, numbers as text, empty fields, or the trigger delivering a field under another name.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What happens when a filter's condition is false?

    A false filter ends the run intentionally; it is not an error.
  2. 2. Why can '9 is greater than 10' be true in a filter?

    Text comparison is alphabetical; use numeric operators or convert first.
  3. 3. Which operator guards against empty fields?

    An exists rule checks that the field has a value.
  4. 4. Where is the best place for a filter that removes irrelevant events?

    Early filters stop unneeded work and save tasks.

Summary

  • A filter lets a run continue only when conditions are true; otherwise it stops quietly.
  • Combine rules with AND groups and OR alternatives; keep them readable.
  • Watch case, whitespace, text versus number, empty values and date formats.
  • Filter early and before irreversible actions; use Paths for true branching.

Next: Paths: Branching Logic