Automations
Multi-step workflows that execute automatically based on triggers. Available on Pro plans and above.
Triggers
An automation starts when a trigger fires:
| Item created | When a new item is added to the pipeline |
| Item updated | When an item's fields change |
| Stage changed | When an item moves to a specific stage. Optionally filter by from stage, to stage, or both |
| Status changed | When an item's status changes. Optionally filter by from status, to status, or both |
| Scheduled | Runs on a recurring cron schedule with a configurable timezone |
| Date field | Fires when a date field value is reached, with an optional offset in days |
Stage and status trigger options
- From stage/status: only fire when the item leaves this specific stage or status. Leave blank to match any.
- To stage/status: only fire when the item enters this specific stage or status. Leave blank to match any.
- You can set both, one, or neither for flexible matching.
Scheduled trigger options
Uses cron expressions for recurring schedules. Select a timezone from the available list: UTC, Europe/Berlin, Europe/London, Europe/Paris, Europe/Zurich, Europe/Vienna, America/New_York, America/Chicago, America/Denver, America/Los_Angeles, Asia/Tokyo, Asia/Shanghai, Australia/Sydney.
Date field trigger options
- Field: select any date field from your blueprint
- Offset days: fire this many days before (negative) or after (positive) the date value
Steps
Each automation is a sequence of steps executed in order:
| Action | Do something: send email, change stage, assign user, and more |
| Wait | Pause for a duration (minutes, hours, or days) |
| Wait until | Pause until conditions are met, with an optional timeout |
| Condition gate | Continue only if conditions are true. Choose to stop or skip the step on failure |
| Branch | Split into different paths based on conditions (then/else) |
Wait step
Pause execution for a set duration:
- Configure in minutes, hours, or days
- The automation resumes automatically when the duration elapses
Wait until step
Pause until one or more conditions become true:
- Set conditions using the same operators as condition gates (see below)
- Set an optional timeout in seconds (default: 24 hours). If the timeout is reached without conditions being met, the step is skipped
Condition gate
Evaluate conditions before proceeding:
- Conditions: one or more field/operator/value checks (see condition operators below)
- On fail: choose stop (end the automation) or skip (skip this step and continue)
Branch step
Split into two paths:
- Conditions: one or more field checks
- Then steps: actions to execute if all conditions match
- Else steps: actions to execute if conditions do not match
- Both paths support any action types
Actions
Available actions within automation steps:
| Change stage | Move the item to a different stage |
| Change status | Set the item's status |
| Assign user | Assign a team member. Strategy can be round-robin |
| Send email | Send an email using a template. Recipient: item contact email, assigned user, or custom email address |
| Create proposal | Auto-generate a proposal from a template |
| Create invoice | Auto-generate an invoice from a template |
| Send webhook | POST item data to an external URL |
| Send notification | In-app notification to the assigned user or item creator |
Condition operators
Conditions are used in condition gates, wait-until steps, branches, and goal conditions:
| Equals | Exact match |
| Not equals | Does not match |
| Contains | Value contains the text |
| Not contains | Value does not contain the text |
| Starts with | Value begins with the text |
| Ends with | Value ends with the text |
| Is one of | Value matches any in a comma-separated list |
| Is not one of | Value does not match any in a comma-separated list |
| Greater than | Numeric comparison |
| Less than | Numeric comparison |
| Is empty | Field has no value |
| Is not empty | Field has a value |
Condition fields
Conditions can check:
- Built-in fields: name, email, phone_number, contact_type, source
- Custom fields: any field defined in the pipeline's blueprint (referenced by field name)
Email template variables
When an automation sends an email, the following variables are available in the template:
| {contact_name} | Name of the contact linked to the item |
| {contact_email} | Email of the linked contact |
| {item_title} | Item title |
| {stage_name} | Current stage |
| {status_name} | Current status |
| {assigned_to} | Assigned user |
| {company_name} | Your company name |
Automation settings
| Name | Descriptive name for the automation |
| Pipeline | Which pipeline this automation belongs to (set at creation, cannot be changed) |
| Enabled | Toggle on/off without deleting |
| Re-enrollment | Allow items to trigger the automation multiple times (default: off) |
| Priority | Set by dragging automations to reorder. Higher priority automations execute first |
| Goal conditions | Optional success criteria using the same condition format as gates. Used to track whether the automation achieved its goal |
Automation templates
Ready-made templates to help you get started:
| Email follow up | Sends a follow-up email after a configurable delay if the item is still open |
| Stale deal reminder | Notifies the assignee when an item hasn't moved stages within a set period |
| Lead assignment | Automatically assigns new items to team members based on field values |
| Proposal follow up | Sends a reminder email after a proposal has been sent but not yet accepted |
Select a template when creating a new automation and customize it for your workflow. You can also start with a Blank Automation.
Example workflows
Follow-up email after 3 days
- Trigger: Item created
- Wait: 3 days
- Condition gate: Status is still "Open" (on fail: stop)
- Action: Send follow-up email template
Auto-assign based on source
- Trigger: Item created
- Branch: Check source field
- If "Website" → Assign to Sales Team A
- Else → Assign to Sales Manager
Stale deal reminder
- Trigger: Scheduled (daily at 9 AM, your timezone)
- Condition gate: Item hasn't moved stages in 14 days
- Action: Send notification to assignee ("Deal needs attention")
Proposal auto-generation on stage change
- Trigger: Stage changed (to "Proposal")
- Action: Create proposal from default template
- Action: Send notification to assignee ("Proposal created, review and send")
Run history
Each automation tracks its execution history. Open an automation's summary dialog to see:
- A visual workflow diagram showing the trigger, conditions, and each step with icons
- Run history with status filter (All, Running, Waiting, Completed, Failed, Cancelled)
- Expandable run details with a step-by-step timeline showing what happened at each step
- Running or waiting instances can be cancelled at any time
Managing automations
- Go to Settings → Company Settings → Automations
- Create new automations from a template or blank
- Toggle automations on/off without deleting them
- Duplicate an automation to use as a starting point
- Reorder automations to control execution priority when multiple automations share a trigger