Skip to main content

Trigger when a record is updated

Start an automation the moment a record changes. Choose the fields that count, then add a filter so it only runs when a value changes to what you need.

Written by Leo

When a record is updated is a trigger that starts an automation every time a record in a database app changes (the trigger decides when an automation starts, and the filter decides whether it continues). It's meant to help you react to changes as they happen, without checking records by hand.

You can use this trigger for many things, including:

  • Notifying the listing agent when a property's status changes to Under contract.

  • Creating an onboarding task when a candidate moves to the Hired stage.

Creating an automation in the Expenses database app: clicking the automations icon, New automation, and When a record is updated. The trigger reads When a record is updated and Expense has changed in Expenses

Note:

  • Choose the fields that count. With Any field, every edit starts a run, even fixing a typo in the title.

  • A manual run doesn't change the record. Filters like Has changed and Has changed to don't match when you test with Manual run. Change a test record instead.

  • Records that are still being created don't count. Changes to a record start the automation only once the record has been created.

Who can use the When a record is updated trigger?

  • 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, run, or delete automations, you need to be a Workspace admin in the workspace the database app belongs to. Only workspace admins see the automations button in a database app.

Set up the When a record is updated trigger

To set up the trigger:

  1. Open the database app on desktop or web and click the automations icon in the top bar (tooltip Create and view automations).

  2. Select New automation.

  3. Select When a record is updated from the list of events.

  4. Select the field name in the trigger to choose which changes count. Learn more about choosing fields below →

  5. Add a filter if the automation should only continue for certain values. Learn more about filters below →

  6. Select Add action and choose what should happen.

  7. Select Create automation.

The list of all nine triggers in a new automation, with When a record is updated marked

The trigger When a record is updated in an expense approval automation

Choose which changes start the automation

The trigger reads like a sentence: When a record is updated and {field} has changed in {app}. Select the field to open the field picker:

  • Any field will start the automation on every change to the record, whichever field changed. This also counts changes to calculation fields.

  • Selecting one or more fields in the list will start the automation only when at least one of them changes. Changes to other fields are ignored.

Selecting the field Status in the trigger opens the field picker with Any field and the fields of the Expenses app

Tip: Pick specific fields whenever you can. Fewer runs means less noise and less risk of delays across your organization.

Filter the When a record is updated trigger

The filter decides whether the automation continues after it's been triggered. Under And if the following conditions are met, select Add filter and build a condition: Where {field} {option} {value}.

For a status field, you can choose from these options:

  • Has changed means the status was changed in this update, to any value.

  • Has changed to means the status was changed in this update to the value you pick.

  • Is and Is not check the current status, whether or not it changed in this update.

  • Is any of and Is none of check the current status against several values.

  • Is completed and Is incomplete check whether the current status counts as done.

  • Is empty and Is not empty check whether a status is set at all.

The options of a Status filter, with Has changed to marked

Other field types offer the options that fit them. Add more filters to combine conditions, or select Add filter group for rules with several parts. Learn more about filters →

Tip: Use Has changed to when something should happen once, at the moment of the change. Is only checks the current value, so a task that's already Done matches Is Done again with every later edit.

Let's look at an example

Let's say you want the team to see when a task is finished. Here's how:

  1. Set the trigger to When a record is updated and Status has changed in Tasks.

  2. Add the filter Where Status Has changed to Done.

  3. Select Add action → Add comment. The action reads Add a comment to the current record. Enter "This task is done: ", then type @ and insert the Title field.

  4. Select Create automation.

The finished automation: When a record is updated with Status, the filter Status has changed to Done, and a comment action

The next time someone sets a task to Done, you should see the comment on the task!

When a record is updated errors

  • If the status below the automation's name shows Broken in red, part of the automation doesn't fit, for example a selected field that has since been deleted. The part that doesn't fit is shown in red. While the automation is Broken, it doesn't run.

  • If a run fails, you can see each step and its message in the automation's runs. To see the runs of an automation, click ▷ next to Manual run at the top right of the editor (tooltip View all runs), or use cmd/ctrl + 1. The Runs panel lists the runs of the last 30 days. Select a run to see each step and its message. To see the runs of all automations, select Runs in the sidebar of the Automation Center.

  • Lots of automation activity in a short time can delay automations across your organization. The delay is temporary. Tape checks the load again shortly and runs waiting automations automatically.

Clicking the runs button next to Manual run to open the Runs panel, opening a failed run, and expanding the failed step Create a record to read its error

Test, pause, edit, or delete an automation with this trigger

  • Manual run runs the automation once on the records you choose. It has real effects. In the example, though, the filter Has changed to doesn't match in a manual run, so no comment is posted. Change the status of a test task instead.

  • New automations you create in the editor are Active right away. To pause one, select Active below the automation's name, then select Save changes. The status switches to Paused. Select it again and save to turn the automation back on.

  • To edit an automation, open the database app, click the automations icon in the top bar (tooltip Create and view automations), then select the automation. Select Save changes when you're done.

  • To delete an automation, open it and click ••• at the top right, then select Delete. Confirm with Delete. You can also click ••• next to the automation in the list of automations, then select Delete. Deleting can't be undone.

Selecting the status Paused below the automation name Expense approval switches it to Active, then the pointer moves to Save changes

Learn more

FAQs

How do I run an automation only when the status changes to a certain value?

Set the trigger to the status field, then add the filter Where Status Has changed to and pick the value.

Can one automation react to changes in several fields?

Yes! Select several fields in the field picker. The automation starts when any of them changes.

Why does my automation run too often?

If your automation runs more often than expected, it could be because:

  • The trigger is set to Any field. Select only the fields that matter instead.

  • The filter uses Is instead of Has changed to. Switch to Has changed to so it only matches at the moment of the change.

What's the difference between this trigger and When a record is created?

When a record is created runs once for each new record. When a record is updated runs on changes to records that already exist.

Are there other triggers I can use?

Yes! An automation can start when a record is created, updated, or deleted, when a comment is added, when a date arrives, on a schedule, and more. See every trigger in Automation triggers →

Are you a developer using the Tape API for automations?

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

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

Did this answer your question?