Sales Automation
Sales Automation lets you define rules that react automatically to events in the pipeline — for example: as soon as a deal moves into a certain stage, a task is created or an email is sent automatically. This means recurring sales steps no longer need to be triggered manually.
What can I do here?
- Create, edit, and (de)activate automation rules
- Set a trigger and an action for each rule
- Search rules and see their status (active/inactive) and execution counts
- Check the execution log to see when a rule ran and whether it succeeded
Step by step
- Click "New Rule", give it a name, and choose a trigger (e.g. "Deal Stage Changed", "Deal Value Above Threshold", "Form Submitted").
- Choose the action to run when the trigger fires (e.g. "Move to Stage", "Assign to User", "Create Task", "Send Email").
- Save the rule and switch it on via the "Active" toggle.
- Go to the "Execution Log" tab to verify the rule is firing as expected, or to investigate failed executions.
Fields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Name / Description | The rule's name and explanation | |
| Trigger | The event that starts the rule | See "Values & statuses" below |
| Action | What happens automatically when it triggers | See "Values & statuses" below |
| Active | Whether the rule is currently applied | Inactive rules no longer fire |
| Executions | How many times the rule has fired so far | |
| Last Run | Timestamp of the most recent execution | |
| Execution Log | List of all rule executions with status, timestamp, and any error message | See "Values & statuses" below |
Values & statuses
Trigger (sales_automation_trigger)
Deal Stage Changed, Deal Created, Deal Value Above Threshold, Deal Inactive (Days), Contact Created, Activity Completed, Email Opened, Email Clicked, Form Submitted.
Action (sales_automation_action)
Move to Stage, Assign to User, Send Email, Create Task, Add Tag, Update Field, Send Notification, Wait Days.
Log status (sales_automation_log_status)
| Value | Plain-language meaning |
|---|---|
| Success | The action was executed |
| Failed | The action could not be executed |
| Skipped | The rule fired but the action wasn't executed (e.g. because conditions weren't met) |
Frequently asked questions
What's the difference to the "Automation Rules" page?
Automation Rules (CRM) covers both support and CRM automations with conditions and multiple action types. "Sales Automation" is a standalone, simpler page specifically for pipeline triggers and actions with its own execution log.
Why didn't an active rule fire?
Check the execution log — it shows whether the rule was skipped or never triggered at all, along with the reason if it failed.
Can I define several actions per rule?
Each rule on this page is tied to exactly one trigger and one action; for more complex condition/action chains, use Automation Rules (CRM).