We recommend building automation examples directly in AI chat. Just describe the workflow 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 workflow automatically. You can review the generated script, test it with real data, and enable the workflow when ready.
A workflow 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 āAll Fieldsā.
Problem: A workflow sends a notification when the Status field changes. With āAll Fieldsā selected, it also triggers when someone edits the Description or adds a comment.
Fix: Set Watch Fields to Status only. Now the workflow ignores all other changes.
Use Filters
Add a filter to any record trigger to narrow which records activate the workflow.
Problem: A workflow processes all new records, but some are test entries.
Fix: Add a filter: Type is not Test. Only real records trigger the workflow.
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.
