With this new update, you can reduce background noise in your organization and optimize automation performance.
The trigger ‘When a record is updated’ can create a certain performance overhead, starting every time a record is updated — even if the filter conditions weren’t met.
Here’s a simple example for non-technical users:
- Imagine an app with 20 fields.
- Automation: If a record is updated and the Status field changes to “Done,” then change the date field.
- Even if you updated one of the 19 other fields, like “Notes” or “Due Date,” the automation would start running in the background, only to stop once it reached the filter.
Just a heads-up, in Tape, you can use this trigger even when calculation fields get updated.
Now, you can select the exact field(s) you want this trigger to watch for updates.
This way, automations only run when those specific fields are updated, reducing background activity and saving valuable resources for your organization.
To take advantage of these benefits, update your existing automations with the “record updated” trigger to use the new filters (see the video above)
Quick Tip: We updated 100+ automations in our own organization in under an hour by using the keyboard shortcut (cmd/ctrl + S) to save changes. 