Zap filters are not working properly
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
Your Zap contains a filter, but it does not follow the filter's conditions when it runs. As a result, the rest of the Zap does not run as expected. The Zap run status shows as Filtered in the Zap history.
In your Zap run, you may see also (missing value)
where the field data should be.
Causes
This can happen for different reasons:
- Mismatched field data: The mapped field’s name changed since the Zap setup, causing the previous mapping to fail.
- Missing data: The app did not send any data to Zapier. This will appear in the Zap run as
(missing value)
. - Incorrect filter condition: Your filter condition did not match your intended goal. For example, you selected AND+ when you meant OR+.
- Mapped field data contains whitespace: Whitespace refers to non-visible characters (like spaces, tabs, and newlines) that affect text formatting and positioning. Though not visible when reviewing your data in Zapier, these characters can be present in mapped fields.
How to fix it
To fix this issue:
-
View the Zap run details. In the trigger or action step where you’re mapping a field from, review the Data Out tab to check how the data was sent to Zapier.
- To check for whitespaces, highlight the field by clicking and dragging your cursor over the text. This will make extra white spaces more noticeable.
- If you do have whitespace, add a Formatter step to trim your text.
- If you find
(missing value)
:- To prevent your Zap from running when there is no value for a mapped field, adjust your filter to add a Does not exist condition.
- Alternatively, remap your fields to one that consistently passes data.
- To check for whitespaces, highlight the field by clicking and dragging your cursor over the text. This will make extra white spaces more noticeable.
-
Review the Filter and path rules in Zaps.
- Check if your filter follows the right condition based on the type of data.
- Certain filter rules work better with text, while others are meant for numbers.
- Check you are using the AND or OR logic correctly.
- Learn more about the difference between AND or OR logic.
- If you have multiple paths, check if the path rules work as intended.
- Learn more about creating path rules.
- When filtering on dates, check that the value is the same format as the condition.
- If date values are inconsistent, add a Formatter step to unify the format each time the Zap runs.
- Check if your filter follows the right condition based on the type of data.
- Test your Zap: Get a new test record and re-test your filter to ensure it works as expected with the correct mapped fields.