Filters Types

Working with filters can be confusing. Here's a guide explaining more about the different conditions you can use.

Below would be a list of the filter conditions. To demonstrate how the condition works, a value will be specified. Different fields would then be supplied to be tested against the value.

Contains

value: brown fox

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will go through because the field contains the value.

If your field is "jumps over the lazy dog," the Zap will not continue to the next step because the field does not contain the value.

Does not contain

value: brown fox

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will not continue to the next step because the field in this instance, contains a value you've asked your Zap to watch for and not continue if it is found.

If your field is "jumps over the lazy dog," the Zap will continue to the next step because the field does not contain the value "brown fox"

Exactly matches

value: The quick brown fox

Note: this filter is case sensitive.

If your field is "The quick brown fox", the Zap will continue to the next step because the field in this instance, exactly matches the value.

If your field is "The quick lazy dog," the Zap will not continue to the next step because the field does not exactly match the value.

Does not exactly match

value: The quick brown fox

Note: this filter is case sensitive.

If your field is "The quick brown fox jumps over the lazy dog," the Zap will not continue to the next step because the field exactly matches the value.

If your field is "The quick lazy dog", the Zap will not continue to the next step because the field in this instance, does not exactly match the value.

Exists

The “exist” condition does not have a value. Its purpose is to let the Zap proceed if there is a field and filter out data if there's none

If your field has any data for the value, the Zap will continue to the next step because the field exists.

If your field does not contain data the Zap will not continue to the next step because the field does not exist.

Does not exist

The “does not exist” condition does not have a value. Its purpose is to filter out the field if it exists or let the Zap continue to the next step if that field does not exist.

If your field contains data, the Zap will not continue to the next step because data for the field exists.

If your field does not contain data the Zap will go through because data for the field does not exist.

Starts with

value: The quick

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will continue to the next step because the field starts with the value

If your field is "The lazy dogs jumps" the Zap will not continue to the next step because the field does not start with the value

Does not start with

value: The quick

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will not continue to the next step because the field starts with the value

If your field is "The lazy dogs jumps," the Zap will continue to the next step because the field does not start with the value

Ends with

value: brown fox

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will continue to the next step because the field ends with the value

If your field is "The lazy dogs jumps" the Zap will not continue to the next step because the field does not end with the value

Does not end with

value: brown fox

Note: this filter is not case sensitive.

If your field is "The quick brown fox," the Zap will not continue to the next step because the field ends with the value

If your field is "The lazy dogs jumps" the Zap will continue to the next step because the field does not end with the value

Is in

"Is in" filters are used if you want to see if the incoming data matches a value in a list. For example, if you had 3 values "Value 1, Value 2, Value 3", it will match the filter if the value from the trigger was one of those options. This filter is not case sensitive.

value: apple, banana, carrot

If your field is "banana," the Zap will continue to the next step because the field is in the list (value)

If your field is "durian" the Zap will not continue to the next step because the field is not in the list (value)

Is not in

"Is not in" filters are used if you want to see if the incoming data does not match a value in a list. For example, if you had 3 values "Value 1, Value 2, Value 3", it will match the filter if the value from the trigger was not among the options. This filter is not case sensitive.

value: apple, banana, carrot

If your field is "banana" the Zap will not continue to the next step because the field is in the list (value)

If your field is "durian" the Zap will continue to the next step because the field is not in the list (value)

Greater than Number

value: 100

If your field is "101" the Zap will continue to the next step because the field is greater than the value

If your field is "99" the Zap will not continue to the next step because the field is not greater than the value

Less than Number

value: 100

If your field is "101" the Zap will not continue to the next step because the field is not less than the value

If your field is "99" the Zap will continue to the next step because the field is less than the value

After date/time

value: 12-25-2020 00:30 (MM-DD-YYYY)

shows a filter with the setting 'Only continue if field after 12-25-2020 00:30'

If your field is "12-25-2020 00:31" the Zap will continue to the next step because the field is after the value

Shows a green validation message '12-25-200 00:31(Date/Time) After 12-25-2020 00:30'

If your field is "12-25-2020 00:29" the Zap will not continue to the next step because the field is not after the value

Shows a yellow validation message '12-25-200 00:31(Date/Time) After 12-25-2020 00:30'

Before date/time

This condition needs dates to be in the US month, day, year format. If your date is in a different format, please use our Formatter to convert the date first: https://zapier.com/help/formatter/#date-time

value: 12-25-2020 00:30 (MM-DD-YYYY)

Shows a filter with the configuration 'Only continue if field before 12-25-2020 00:30'

If your field is "12-25-2020 00:31" the Zap will not continue to the next step because the field is not before the value

If your field is "12-25-2020 00:29" the Zap will continue to the next step because the field is before the value

Was this article helpful?
0 out of 0 found this helpful