Review run history
Open Run History to check whether an automation ran and what it found. The table shows the Automation, Run Date, number of Opportunities, and Status for each run. Select a row to open the run details. Use the opportunity count to distinguish a successful run with no matches from a run that processed matching deals.What you’d use one for
- Post to Slack or email every Monday with deals closing this quarter that have not moved a stage
- Create a private Google Doc after each weekly pipeline review
- Flag opportunities over a threshold amount with no activity in two weeks
- Alert a channel when a deal in late stage has a close date in the past
- Remind a team about deals missing a champion or economic buyer
How an automation works
Three parts:1
A schedule
When the automation runs — a cron expression or a recurrence rule, in a timezone you choose.
2
A filter
Which deals it cares about. Built from opportunity, account, and contact fields with comparison operators, and combinable with and / or / not.
3
One or more actions
What happens when deals match. An automation can send a Slack message or email, or create a Google Doc, using literal text or a rendered Canvas template.
Scope
Safety model
Automations are built to be hard to fire accidentally:- New automations are always created disabled. Nothing runs until you explicitly enable one.
- Editing configuration disables the automation again. A half-edited automation cannot run.
- Enabling validates dependencies — if the Slack channel is not connected, or the automation lacks execution authority, enabling fails with a specific blocker.
Where to go next
Build your first automation
A stalled-deal Slack alert, end to end.
Filter reference
Every field, operator, and action available.