Every automation is built from a trigger, which starts it, followed by logic and action nodes that decide what happens next. This article explains what each trigger does and when it fires, then lists the logic nodes and actions you can add after it.
To add a trigger, open an automation and click Add Trigger. After that, click the + button under any node to add logic or an action.
Triggers
There are 81 triggers, grouped by what they relate to. Each one fires at the moment described. If a trigger can be given a timing, such as 30 days before an event, that is noted.
Leads
A lead is created fires when a new lead is added, whether it came from a form on your website or was added by your team
A lead is amended fires when the details of an existing lead are changed
A lead is deleted fires when a lead is deleted
A lead status is changed fires when a lead moves from one status to another, for example when you move it along your pipeline
A lead converts to booking fires when someone on your team converts a lead into a booking. It does not fire when a customer accepts a proposal. For that, use "A proposal is accepted" and "A booking is created"
Bookings
A booking is created fires when a new booking is made, whether by a customer or by your team
A booking is amended fires when the details of a booking are changed
A booking is deleted fires when a booking is deleted
A booking status is changed fires when a booking moves from one status to another
A booking is started fires when a booking reaches its start. You can set it to fire before the start instead, for example 30 days before a booking is started, which is how the 30 day event confirmation automation works. The 14 day payment reminder works the same way
A booking is ended fires when a booking reaches its end. This is the one to use for post-event emails such as review requests
Forms
A form is submitted fires when a customer completes and submits one of your forms
A form is abandoned fires when a customer starts a form but leaves without finishing it. This is how incomplete reservations are captured
A form submission is updated fires when an existing form submission is changed after it was sent
A form widget is submitted fires when a customer submits a form that is embedded on your website as a widget
Proposals
A proposal is created fires when a new proposal is made
A proposal is viewed fires when the customer opens their proposal. Use it to follow up while you are fresh in their mind
A proposal is accepted fires when the customer accepts their proposal
A proposal acceptance fails fires when a customer tries to accept a proposal but it does not go through
A proposal is sent fires when a proposal is sent to the customer
A proposal expires fires when a proposal passes its expiry date without being accepted
Contracts
A contract is created fires when a new contract is generated
A contract is updated fires when a contract is changed
A contract is viewed fires when the customer opens their contract
A contract is signed fires when the customer signs their contract
A contract is deleted fires when a contract is deleted
Invoices
Invoice is due fires when an invoice reaches its due date
An invoice is created fires when a new invoice is made
An invoice is paid in full fires when the remaining balance on an invoice has been paid
An invoice is overdue fires when an invoice passes its due date without being paid in full
Payments
A payment is created fires when a payment is recorded against a booking, including one you add yourself
A payment succeeds fires when a payment is taken successfully, for example a customer paying a deposit by card. Use this one to send a payment receipt
A payment fails fires when a payment attempt does not go through
A payment is refunded fires when a payment is refunded
A payment is deleted fires when a payment record is deleted
Contacts
A contact is created fires when a new contact is added
A contact is amended fires when a contact's details are changed
A contact is deleted fires when a contact is deleted
A contact logs in to the portal fires when a customer logs into their client portal
Tasks
A task is created fires when a new task is added
A task is updated fires when a task is changed
A task is deleted fires when a task is deleted
A task deadline is due fires when a task reaches its deadline
A task is completed fires when a task is marked as complete
Venues
A venue is created fires when a new venue is added
A venue is amended fires when a venue's details are changed
A venue is deleted fires when a venue is deleted
Users and shifts
A user is created fires when a new user is added to your account
A user is amended fires when a user's details are changed
A user is deleted fires when a user is deleted
A user requests a shift fires when a team member asks to work a shift
A user declines a shift fires when a team member turns down a shift they were offered
A user accepts a shift fires when a team member accepts a shift they were offered
A user is assigned to a shift fires when you assign a team member to a shift
A user is removed from a shift fires when a team member is taken off a shift
A user changes a shift fires when a team member's shift is changed
A user starts a shift fires when a shift reaches its start time
A user ends a shift fires when a shift reaches its end time
A user clocks in fires when a team member clocks in to work
A user clocks out fires when a team member clocks out
Artwork
Artwork Added fires when artwork is uploaded to a job, for example by a customer in their client portal
Artwork Updated fires when artwork on a job is changed or replaced
Artwork Add Comment fires when a comment is added to artwork
Artwork Accepted fires when artwork is approved
Templates, backdrops and start screens
A template is chosen fires when a template is selected for a job
A template choice is deleted fires when a selected template is removed from a job
A backdrop is chosen fires when a backdrop is selected for a job, for example by a customer in their client portal
A backdrop choice is deleted fires when a selected backdrop is removed from a job
A startscreen is chosen fires when a start screen is selected for a job
A startscreen choice is deleted fires when a selected start screen is removed from a job
Messages
A message is received fires when a new message arrives in a conversation
Repeating
These run on a schedule instead of waiting for something to happen.
Every day fires once a day
Every week fires once a week
Every month fires once a month
Every year fires once a year
Reps
A rep requests a withdrawal fires when a rep asks to withdraw their commission
A rep withdrawal request is paid fires when a withdrawal request is marked as paid
A rep receives a commission fires when a commission is credited to a rep
Advanced
Catch a Webhook fires when another system sends information to the webhook address for your automation
An upsell is claimed fires when a customer claims an upsell, for example in their client portal
A gratuity is added fires when a tip or gratuity is added to a booking
Logic nodes
Logic nodes sit between the trigger and your actions and control what happens.
If / Else checks a condition and sends the automation down the true path or the false path. The starter Deposit Reminder automation uses it to ask "Deposit still unpaid?" before sending a reminder
Wait pauses the automation for a set time before the next step, such as 2 days or 7 days
Split splits the automation into separate paths
Format Number and Format Date change how a number or date appears in your messages
Chat GPT uses AI as a step in your automation
Actions
Sending messages
Email sends an email, for example to the customer or to you. The starter automations use "Email to Customer" and "Email to Admin"
SMS sends a text message, using your connected SMS account
WhatsApp sends a WhatsApp message
Send Conversation Message sends a message into a conversation with the customer
Pushover sends a push notification to your device
Marketing tools
Mailchimp, Active Campaign and Mailerlite connect the automation to your account in that tool
Proposals
Send Proposal sends a proposal to the customer
Create Proposal creates a new proposal
Records and data
Change Field Data updates a field on a record
Fetch entity looks up a record
Create entity creates a new record, such as a lead, booking or contact
Work and staff
Create Task adds a task
Create a Shift adds a shift
Store items
Assign a Package adds a package to the record
Assign a Product adds a product to the record
Connecting to other tools
Webhook sends the details of what happened to another system

