While editing a sales pipeline, stage automations control what must happen when leads or deals enter or leave a stage. Configure them in the pipeline editor’s automation section.
Please note:
- Automations are per pipeline and object type (lead vs deal).
- Overly strict required fields block board moves — train reps before enabling.
- Deal-only and lead-only automation types do not appear on the other object type.
Automation types
| Type | Lead | Deal | Purpose |
|---|---|---|---|
| Required Properties | ✓ | ✓ | Block stage entry until fields are set |
| Stage Movement Rules | ✓ | ✓ | Restrict which stage transitions are allowed |
| Activity Logging | ✓ | ✓ | Require/prompt activity when entering a stage |
| Auto-assign Owner | ✓ | ✓ | Assign owner automatically |
| Create Task Automatically | ✓ | ✓ | Spawn a task on stage entry |
| Create Payment | ✓ | Create a payment when a deal enters the stage | |
| Auto-Create Deal | ✓ | Prompt to create a deal when a lead enters the stage | |
| Update lead properties | ✓ | Set lead fields (for example inactive) on stage entry |
Configure
- Open Configuration → Pipelines → edit a pipeline.
- Open Automations (or the automation panel on the editor).
- Add an automation, pick type + stage, and fill its config.
- Save the pipeline.
- Test by moving a sample lead/deal through the stage on the board.
flowchart LR
Enter[Enter stage] --> Rules{Automations}
Rules --> Req[Required fields]
Rules --> Task[Auto task]
Rules --> Own[Auto-assign]
Rules --> Deal[Lead → deal prompt]
For broader cross-module logic beyond stage entry, see Build your first workflow and Workflow approvals.