Filters and paths are both tools that can be used for conditional or branching logic in your Zaps. This allows you to ensure actions get performed only on the items you want. Both tools use filters to set specific conditions to get the granularity you need.
For instance, you can set up a filter to only capture emails that contain a specific subject line or only customers who purchase a specific product. So when the data from your Zap meets the conditions of a filter, it proceeds to the next action in your Zap. If a filter stops an item, then no further actions are performed.
Using either tool doesn't towards your task usage.
Filter rule types
Filters can use different rules for logic. Conditions can only work for the type of data that is specified in parentheses. There are five types of filter rules: text, number, date/time, boolean, and generic.
In this table, you can see which fields would pass a given rule. In each example, the Rule is the filter rule we’ve set, the Value is what we’re checking against, and the examples are those coming through the Zap that the filter is checking.
|Examples that would pass
|Examples that wouldn’t pass
|Apples and bananas
|Apples Apple Apples and bananas
|(Text) Does not contain
|Apples and bananas
|(Text) Exactly matches
|Apple (not plural) apple (not uppercase)
|(Text) Does not exactly match
|Apple Banana And more
|(Text) Is in
|Apple Banana Strawberries
|(Text) Is not in
|(Text) Starts with
|(Text) Does not start with
|(Text) Ends with
|Bananas Apple and bananas
|(Text) Does not end with
|(Number) Greater than
|(Number) Less than
|01/01/2019 12/31/2018 01:01
|12/31/2019 12/31/2018 00:00
|Apple 10 01/01/2019
|Does not exist
|Apple 10 01/01/2019
Text filters only work with text data, so they won’t work with numbers or dates.
- Contains: Checks if the field contains a value. This is not case-sensitive.
- Does not contain: The opposite of Contains, this checks that the field does not contain a value. This is not case-sensitive.
- Exactly matches: Checks if the field matches a value letter-for-letter. This is case-sensitive.
- Does not exactly match: Checks if the field does not match a value letter-for-letter. This is case-sensitive.
- Is in: Checks if a field is in a list of values. This is not case-sensitive.
- Is not in: Checks if a field is not in a list of values. This is not case-sensitive.
- Starts with: Checks if a field begins with a certain value. This is not case-sensitive.
- Does not start with: Checks if a field does not begin with a certain value. This is not case-sensitive.
- Ends with: Checks if a field ends with a certain value. This is not case-sensitive.
- Does not end with: Checks if a field doesn’t end with a certain value. This is not case-sensitive.
You should only use Exactly matches as a filter rule when you want your Zap to continue only if the field has certain exact words, down to the letter (it's even case-sensitive). Be careful with this rule as it can sometimes filter out more records than you expect. If you want a similar but less strict rule, try using Contains.
Number filters only work with numeric values, like 1 or 100. They do not work with written forms of numbers (one, two, one hundred) or dates.
- Greater than: Checks if a field is greater than a certain number.
- Less than: Checks if a field is less than a certain number.
- After: Checks if a date is after a certain date.
- Before: Checks if a date is before a certain date.
- Equals: Checks if two dates are identical.
- Is true: Checks is a boolean value is true.
- Is false: Checks if a boolean value is false.
- Exists: Checks if a value exists (can be used with any type of field).
- Does not exist: Checks if a value doesn’t exist (can be used with any type of field).
Filters and line items
If you have a set of line items like this:
Whether your Zap continues past the filter depends on whether you use positive or negative filter conditions.
- Examples of positive filter conditions are “Contains” and “Starts with”.
- Examples of negative filter conditions are “Does not contain” and “Does not start with”.
If your filter conditions are all positive
If all conditions are positive, at least one line item must pass all filter conditions for the Zap to continue.
In the example below, the Zap continues because a single line item passed both positive conditions, even if others didn't.
If your filter conditions are both positive and negative or all negative
Whenever there is a negative condition included, all line items must pass all filter conditions for the Zap to continue.
In the example below, the Zap doesn't continue because at least one line item didn't pass the filter conditions.
You can use Formatter to convert line-items to text if you need to filter on all line items.
The Filter action doesn't remove any line items. If you map line items to later actions, this will include any line items that didn't pass the filter conditions.