On the Team plan and above, an automation can react to what happens in your contact book and change it for you. A new lead gets a tag and a follow-up task. A person who moves to Customer gets an owner. A lost deal leaves a note. Automations are built in the same builder as any other automation. See Automations overview.
Triggers
An automation can start when:
- A contact is created
- A contact is updated
- A contact is tagged
- A contact loses a tag
- A contact is added to a list
- A contact is removed from a list
- A contact changes owner
- A contact moves to another stage
- A contact grants or withdraws consent
- A task is due
- A deal is created
- A deal moves to another stage
- A deal is won
- A deal is lost
Each trigger starts a run once per event, so a change is not announced twice.
Actions
| Action | What you set |
|---|---|
| Tag the contact | The tag name. It is created if your workspace has no tag with that name. |
| Remove a tag from the contact | The tag name. A tag that does not exist is skipped. |
| Set the contact owner | The email address of a team member who can open the contact. Leave it empty to clear the owner. |
| Set the contact stage | The name or key of a lifecycle stage. Leave it empty to clear the stage. |
| Create a task | A title, details, how many days from now it is due (0 to 365), and the email address of the assignee. Without an assignee it goes to the contact's owner, then to whoever built the automation. |
| Add the contact to a list | The name of a list that already exists. The step fails when there is no such list. |
| Add a note to the contact | The note text, plain text up to 4,000 characters. |
Which contact an action acts on
- For a contact trigger, the contact itself.
- For A task is due, the contact the task is linked to.
- For a deal trigger, the contact the deal is linked to.
When there is no contact, for example a task that belongs to nobody, the step is skipped instead of guessing.
Use details from the trigger
Any text field in an action can contain placeholders. They look like
{{ trigger.subject.email }}. The subject is the contact, task or deal that started the run, and
the facts about the event itself sit directly under trigger.:
| Placeholder | What it gives you |
|---|---|
{{ trigger.subject.email }} |
The contact's email address |
{{ trigger.subject.title }} |
The title of the task or deal |
{{ trigger.tag }} |
The tag that was added or removed |
{{ trigger.list }} |
The list a contact was added to or removed from |
{{ trigger.to }} |
The stage a contact moved to |
{{ trigger.status }} |
The new consent status |
Example: a note that says Tagged {{ trigger.tag }} on the trigger A contact is tagged.
Safe by design
- Creating a task or a note is never repeated by a retry or by an event that is delivered twice.
- If a contact is erased while a run is waiting to act on it, the run is cancelled.
- Marketing email stays limited to people who agreed. A step that sends marketing email skips everyone without recorded consent. See Notes and consent.
- The plan is checked every time an action runs, not just when you save it. If your workspace moves below Team, the CRM actions stop and say so.
- The events themselves carry no email address or phone number. The contact's details are read when the run starts and stay with that run.
