Skip to main content

Automations

An automation starts from a trigger and runs steps: actions, delays and branches. Find them under Automations in the sidebar.

Triggers​

TriggerFires when
Record created / Field changedA CRM record is created, or a field changes (optionally to a specific value)
Deal stage changedA deal moves to a stage
Joined a list / Left a listA record enters or leaves a CRM list
Contact emailed you / Meeting bookedMail or a meeting with a contact is logged from a connected mailbox
Document opened / accepted / declinedA CRM document changes state
On a scheduleAt set days and times, for matching records
Form submittedA form receives a non-spam submission
CMS entry publishedContent is published in the CMS
Social message receivedA comment, DM or review arrives in the Social inbox
Incoming webhookAnother system POSTs to the automation's private URL
Manually or from the APIYou start it from a record, a bulk action, or the CRM API

Actions​

  • CRM: create or update contact, update a field, set or rotate owner, create task, add note, create deal, add to or remove from a list, start a sequence, score with AI, send to another CRM.
  • Messages: send email, notify teammates, reply in the Social inbox.
  • Developer: send webhook, run code (JavaScript).
  • AI: generate text with AI (the result can be used in later steps).

Use delays (for a period, until a date, or until a time of day), wait until (pause until conditions are met, with a time-out) and branches (if/else on any field, trigger data or variable) to shape the flow.

Values from earlier steps​

Insert values with merge tags: {{record.first_name}}, {{data.message}} (trigger data), {{vars.ai}} (a saved step result). A fallback goes after a pipe: {{record.first_name | there}}.

Testing, history and versions​

  • Test run runs the automation for a record you pick, so you can check each step.
  • Activity lists every run with a step-by-step log. Steps set to need approval (for example AI-written emails) wait in the review queue until someone approves or rejects them.
  • Edits are saved as a draft. Publish makes them live as a new version (v1, v2…) without affecting runs already in progress; Discard changes goes back to the live version.

Each run counts towards your plan's monthly automation runs. Emails sent by automations include an unsubscribe link when they are marketing emails, and contacts on the do-not-contact list are skipped.