Skip to main content
We recommend building automation examples directly in AI chat. Just describe the automation you want, and AI will handle the full setup for you, including the trigger, actions, script, and configuration.

Build with AI

Open the AI Chat in your table’s right sidebar and tell AI what you want. For example, you can say: “When the Status field changes to Approved, send a notification email to the assignee. Only trigger on Status changes, ignore other field edits” AI will create the complete automation automatically. You can review the generated script, test it with real data, and enable the automation when ready. An automation that triggers too often wastes runs, sends unwanted emails, and creates noise. Here’s how to keep triggers precise.

Use Watch fields

When using When record updated, always select specific fields instead of clicking Watch all. Problem: An automation sends a notification when the Status field changes. With all fields watched, it also triggers when someone edits the Description or adds a comment. Fix: Set Watch fields to Status only. Now the automation ignores all other changes.

Use Filters

Add a filter to any record trigger to narrow which records activate the automation. Problem: An automation processes all new records, but some are test entries. Fix: Add a filter: Type is not Test. Only real records trigger the automation.

Combine Both

For maximum control, use watch fields and a filter together:
  • Watch fields: Status
  • Filter: Status is Approved
This means: only trigger when the Status field changes and the new value is “Approved”.

Use “When record matches conditions” for State Changes

If you want to trigger only on the transition (e.g. from “Pending” to “Approved”), use the When record matches conditions trigger instead. It fires once at the moment the record begins to match — not on every subsequent edit.
Last modified on November 11, 2026