How to create custom automations
Custom automations let a milestone in your pipeline start the next step without manual handoffs. Choose a trigger, choose an action, and narrow the audience with suppressions so the right people receive the right follow-up.
Pick a trigger, then an action
Start with the event that should start work. A lead status, a project status, or a meeting can act as the milestone. Once that milestone is reached, the automation can send an email or SMS, create a to-do task, add an item to a call queue, or change a lead or project status automatically.
Use suppressions to target precisely
Suppressions add targeting control. You can limit an automation by class, project type, or lead source. Select the relevant group in the dropdown, and the automation runs only for recipients carrying that label. This helps prevent a general follow-up from reaching people for whom it does not apply.
Review and manage existing automations
Keep a short pre-launch checklist: confirm the trigger milestone, confirm the action and recipient, check any suppression labels, and test with a known record before relying on it for live work. To review or change existing automations, go to Admin > Automations.
| Trigger milestone | Possible actions |
|---|---|
| Lead status | Send email, send SMS, create to-do task, create call-queue item, update lead status |
| Project status | Send email, send SMS, create to-do task, create call-queue item, update project status |
| Meeting | Send email, send SMS, create to-do task, create call-queue item, update status |
Actions listed are those described for custom automations; availability may vary by account configuration.
Frequently asked questions
What workflow automations are worth setting up first?
A welcome text when a lead reaches Lead Received, an email when a project status changes, and a to-do task created after a meeting are practical starting points.