Automations

An automation is a rule: when something happens to a record, if it matches your conditions, do one or more actions. Rules live under Settings, Automations, and only the workspace owner can manage them.

Triggers

Record	Trigger	Fires when
Contact, Lead, Deal	Created	The record is created, from the app, the API, an import or a connected assistant.
Contact, Lead, Deal	Updated	Any field on the record changes.
Contact, Lead	Reply received	An email reply from the record lands in the inbox.
Deal	Stalled	An open deal has had no activity and no open task for the number of days you set. Fires once until the deal moves.
Deal	Time in stage	A deal has sat in the chosen stage for at least the number of days you set.
Task	Created	A task or appointment is created, from the app, the API, the phone or a connected assistant. Tasks an automation itself creates do not re-trigger it.

Conditions

A condition is a field, an operator and a value. Up to three, all of which must match. Values are matched case-insensitively.

Contacts, leads and deals can test any field on the record, for example status, source, company, lifecycleStage, and your custom fields by their key. On a Reply received trigger, replyClass equals INTERESTED gates on how the reply was classified.
Tasks can test type, priority, title, done and assigneeId. type equals MEETING limits a rule to bookings.

Operators: equals, does not equal, contains, and, for date fields, older than a number of days.

Actions

Action	What it does
Create task	Adds a task, optionally due in a number of days and assigned to the record owner.
Add tag	Tags the record.
Assign (round robin)	Gives the record to the next team member in rotation.
Set field	Sets the record's status.
Send email	Emails the contact on the record. Draft for review saves it to the approval queue; Send automatically sends it with no review.
Notify	Tells a person on your team. See below.
Enroll in sequence	Adds the contact to an active sequence.

Notify

Notify reaches a person, not the customer. Three targets:

Record owner is whoever the record or task is assigned to. If nobody is, the step is skipped and the run says so.
A teammate gets an in-app notification and an email. Each person can turn the email off under Settings, Notifications, Automation alerts.
An email address gets a plain email. This works for addresses outside the workspace, for example a booking desk.

The title becomes the email subject and the body the email body. Both accept the variables below.

Variables

Type a variable in double braces, or click a chip under the field to insert it.

Variable	Value
`{{firstName}}`	The contact's first name
`{{name}}`	The contact's full name
`{{email}}`	The contact's email address
`{{company}}`	The contact's company
`{{title}}`	The task or appointment title, or a contact's job title
`{{when}}`	The task or appointment time, in the workspace timezone. Day only for all-day tasks. Blank when the task has no date.
`{{offering}}`	The offering an email is about, where one is attached

Contact values come from the contact linked to the record. A task with no contact leaves them blank. A variable the system does not know renders blank rather than failing the rule.

Booking alert

To get an email whenever a booking is made through the API or the calendar:

Record Task, trigger Created.
Add a condition: type equals MEETING.
Add a Notify action. Pick your own name, or choose Email address and type where the alert should go.
Title: New booking: {{title}} for {{name}}. Body: {{name}} from {{company}} booked for {{when}}.
Create the automation, then create an appointment with a contact attached to test it.

Troubleshooting

Open Recent runs under a rule. Every run lists its steps as OK or Skipped with a reason, for example "Record has no owner to notify" or "No contact on the record to enroll". A rule whose conditions did not match leaves no run. Automations never fail the action that triggered them: a failing step is recorded and the record change still goes through.