Skip to main content

Filter automations by field changes

Run an automation only when a field was edited, or changed to a certain value. Learn Has changed, Has changed to, and how to check the previous value.

Written by Leo

You can filter changes to let an automation continue only when a field was edited in this update, or was changed to a certain value. Change filters compare the record with its previous revision.

You can use change filters for many things, including:

  • Reacting once when a property's status changes to Under contract, not on every later edit.

  • Starting onboarding only when a candidate's stage was changed to Hired.

This page covers Has changed, Has changed to, and Has changed to any of.

The options of a filter row on Status, with Has changed to marked. Has changed is right above it.

Note:

  • Change filters need a previous revision. The change options work with the trigger When a record is updated. In Conditional actions, they also need Get previous values above the condition. With other triggers, add Get previous values and compare the field's previous value with Is or Is not.

  • A manual run doesn't change the record. Has changed to may not match when you test with Manual run. Change a test record instead.

Who can use filters on changes?

  • Automations are available on all plans: Free, Plus, and Premium. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • To create, edit, pause, or delete automations, you need to be a Workspace admin of the workspace the database app is in and have Full access to every database the automation uses. App permissions alone aren't enough.

Set up a change filter

To filter on a change:

  1. Open the database app and click the automations icon at the top right (Create and view automations), then open an automation.

  2. Set the trigger to When a record is updated. The change options aren't offered with other triggers. Learn more →

  3. Under And if the following conditions are met, select Add filter.

  4. In the new row, select the field and choose the one you need.

  5. Select Has changed, Has changed to, or Has changed to any of.

  6. For the last two, choose the value. Has changed doesn't need one.

  7. Select Save changes.

Add filter adds a row. Status is selected as the field, Has changed to as the option, and Approved as the value.

Choose the right change option

  • Has changed is met when the field's value differs from the value in the previous revision of the record, to any value. It's available for most field types.

  • Has changed to is met when the field changed and the new value is the one you choose. It's available for status, single category, single person, single relation, and Last edited by fields. For the status of task list items, the option is called Item has changed to.

  • Has changed to any of is met when the field changed and the new set includes any of the values you choose. It's available for multiple categories, multiple people, and multiple relations fields.

Fields that never change after a record is created, such as Created at, Created by, and unique IDs, don't offer a change option.

Tip: The trigger When a record is updated has its own field list: it starts the automation when any chosen field changes. A change filter then decides what happens next, for example only when the status changed to Done. Learn more →

Check the previous value

There's no option for a change from a value. To react to a change from a value, such as a status that was New:

  1. Use When a record is updated, or add Get previous values and work in Conditional actions after it.

  2. Select the field in the filter row and choose the field under the previous values of the record, for example Deal previous values, instead of the current one.

  3. Compare it with the value you expect, for example Is New.

The field list of a filter row, searched for Status, shows Status under Expense and Status under Expense previous values.

Let's look at an example

Let's say you want the team to see when a deal is signed, but not when it's edited afterwards. Here's how:

  1. Set the trigger to When a record is updated and Stage has changed in Deals.

  2. Add the filter Where Stage Has changed to Signed.

  3. Select Add filter and add Where Regions Has any of EMEA and APAC.

  4. Select Add action → Add a comment to the current record, then enter "Deal signed: " and insert the Title field.

  5. Select Create automation.

The next time a deal in one of those regions moves to Signed, you should see the comment on the deal!

Change filter errors

  • If you can't find a change option while you're setting it up, check the trigger. The change options only appear with When a record is updated. If you change the trigger later, the automation is marked Broken. Remove the change filter or switch the trigger back, then select Save changes.

  • If a change filter never matches, check the trigger. The filter under the trigger only has a previous revision with When a record is updated. With other triggers, add Get previous values and compare the previous value with Is or Is not. Learn more →

  • If it matches too often, check whether the filter uses Is instead of Has changed to.

Test, pause, edit, or delete a filter

  • To test a filter, change a test record so it matches the condition, then select the runs button at the top of the automation (View all runs) to open Runs. A Manual run doesn't change the record, so Has changed options may not match.

  • To edit a filter, open the database app, click the automations icon in the top bar, then select the automation. Change the field, option, or value, then select Save changes.

  • To delete a filter, select the settings button at the end of the row or group, then select Remove.

Learn more

FAQs

What's the difference between Has changed and Has changed to?

Has changed matches any edit of the field. Has changed to matches only when the new value is the one you choose.

Why doesn't Has changed to match when I use Manual run?

A manual run doesn't change the record, so there's no change to detect. Change a test record instead.

Can I use Has changed with a trigger other than When a record is updated?

No, the change options are only offered with When a record is updated. With other triggers, add Get previous values and compare the field's previous value with Is or Is not in Conditional actions.

Can I check what a field was changed from?

No, there's no option for a change from a value. In the filter row, choose the field under the previous values of the record, such as Deal previous values, and compare it, as described above.

Which field types support Has changed?

Most of them. Unique IDs, Created at, and Created by don't, because their values stay the same.

Where can I find all automation filter options?

In Automation filters →. It explains how to combine rows and groups and links to the options for each field type.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Filters in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?