Short answer
Why Is My Zapier Filter Not Working?
A Zapier Filter usually behaves unexpectedly because the mapped value differs from the visible label, is blank at runtime, has a different data type, or uses AND where OR was intended. Inspect the Filter input in Zap History, copy the exact runtime value, normalize text or numbers before the Filter, and retest both a passing and failing case.
Common causes
- The filter uses stale sample data or maps a similarly named field.
- Whitespace, capitalization, date formats, or numeric text changes the comparison.
- All conditions must pass when the rule should allow any matching condition.
- A missing field arrives as blank rather than the expected false or zero.
Diagnostic steps
- Open a real run and inspect Data In for the Filter step.
- Compare the raw value, type, spaces, and capitalization with the configured condition.
- Add a Formatter step when the source value needs predictable normalization.
- Test one record that must pass and one that must stop before publishing.
Example
A status displays as “Approved” in the source but arrives as lowercase “approved ” with a trailing space. Trim and normalize it before comparing.
Caveats
Testing only the happy path can hide a filter that passes too broadly. Filters stop runs; they do not undo actions that happened earlier.