Skip to main content

Filters

The Filters tab decides which records should continue through to the action stage. If the record does not pass the filter checks, then no actions are taken on it.

Filter Combination​

Set the Filter Combination to control how multiple filters behave together:

  • AND means all filters must match
  • OR means any matching filter can pass the record through

Add Filters​

You can leave the filters section blank, or add as many filters as your flow needs.

It is also possible to apply multiple filters to the same field if you need a more precise result.

Choose the Field and Comparison​

For each filter, select:

  1. the field you want to check
  2. the comparison to use
  3. the value to compare against

You can select the field to filter by from a searchable drop down.

The data type for the field is shown as a tag so you can easily see where the data for that field comes from. Flow understands how the data types are related to each other so you will see a full list of all available fields here.

Once you have selected the field to filter by, you select the comparison type and the value to compare with.

In the example above, we are filtering by the Customer Type field from the Customer data type, and checking if the value is Wholesale.

We are using the is any of comparison, so we can add additional customer types to compare against, and as long as the record matches one of the selected customer types, the filter for this field will pass.

Some filters can also use the value from another field instead of a fixed value. For example, to check if the SalePrice is greater than the CostPrice for a product.

For the full list of comparison options available by field type, see Filter Reference.

Compare One Field with Another​

For supported comparisons, Flow can use the value from another field instead of a fixed value.

This is useful when you want to compare two values on the same record. For example, you could identify products where the sale price is less than or equal to the cost price.

Filter by Empty Fields​

Flow also supports empty-field checks such as is empty or is not set and is not empty.

This is especially useful when you want to target records that need attention because a value has not been filled in yet.

For example, you could identify stock records where the minimum or maximum stock level has not been set.

Date and Time Examples​

The newer date and time comparisons are useful for more precise time-based rules.

Examples include:

  • the first or last day of this month or next month
  • a specific day such as the 10th day of this month or next month
  • records from the last few hours
  • records from the last few minutes

Keep Filters Focused​

When possible, keep the filters aligned to the exact outcome you want.

For example:

  • reporting flows usually focus on selecting the right records for export
  • update flows usually focus on preventing unintended records from being changed
  • delete flows should be checked especially carefully before activation