Automation triggers: every event that can start an automation
An event automation starts when something happens in your account. That something is its trigger, and you pick it when you create the automation: Automation → New automation → Empty automation → Next → Event, then choose from the Events list and click Submit.
A trigger can't be changed afterwards. If you picked the wrong one, build a new automation.
Just want another system to hear about these events? Use a webhook subscription rather than an automation with a webhook in it. See Webhooks: send events from Leat to your own system.
Not everything that happens in Leat is a trigger. If an event isn't in the list below, it can't start an automation, but it may still be reachable another way, because the other two automation types don't use events at all:
- Periodic runs on a schedule and selects contacts with filters instead of waiting for an event. Before you build one, check whether a recurring email or a recurring voucher issuance covers what you want: those are the tools for anything that repeats on a cadence. How to build an automation lists the scheduled work a periodic automation is still the right choice for.
- Manual is started by you on a contact list or a single contact, or by a developer through the Leat API.
Whichever trigger you choose, you narrow it at the Start step with filters: on the contact, and usually on the thing that fired the event too. A contact who doesn't pass the filters doesn't show up in the automation's runs at all.
Loyalty
- Tier reached: a contact moves into a tier. Filter on the contact, or on the tier they reached. Only there if your account uses tiers.
- Loyalty transaction created: points are credited to a contact. Filter on the contact, or on the transaction.
- Points balance increased: a contact's point balance goes up. Filter on the contact.
Contacts
- Contact created: a new contact is added, however they arrived.
- Contact updated: a contact's details change. See the next section.
- Contact subscribed: a contact opts in to a subscription type. You pick which subscription type when you create the automation.
- Contact unsubscribed: a contact opts out of one. You pick the subscription type here too.
Contact updated in detail
Contact updated fires when a contact attribute gets a new value, when the contact's type changes, or when their phone number changes. It doesn't fire when the contact's points, tier or balance change, because those come from transactions: use Loyalty transaction created, Points balance increased or Tier reached for those.
At the Start step you have 2 kinds of filter:
- Contact filters on what the contact looks like now, after the change.
- Attribute has changed lets you pick one or more attributes. The automation only starts when at least one of them was part of this update. Without it, the automation starts on every change to the contact, whatever changed.
A change to the contact's type or phone number alone doesn't pass an Attribute has changed filter, because no attribute changed.
While a contact is going through a Contact updated automation, for example waiting in a delay, further updates to that contact don't start it again for them.
A Set contact attribute or Contact type action in any automation counts as an update, so it can start your Contact updated automations.
Rewards and vouchers
- Digital reward reception created: a contact claims a digital reward.
- Physical reward reception created: a contact claims a physical reward.
- Voucher created: a voucher code is issued to a contact.
- Voucher redeemed: a contact redeems a voucher code.
- Voucher expired: a voucher code passes its expiry date.
The voucher triggers can filter on the voucher and on its promotion.
Referrals
Referrals fire twice, once for each side, and you choose which contact the automation runs on. Getting this wrong is the most common referral mistake: an automation that thanks the referrer but is built on the referred contact will reward the wrong person.
- Referral created: run automation with the contact that has been created. Someone has just been referred.
- Referral created: run automation for the contact that did the referring. The same moment, from the referrer's side.
- Referral completed: run automation with the contact that got referred. The referral has met its conditions.
- Referral completed: run automation for the contact that did the referring. The same moment, from the referrer's side.
Referral triggers can only filter on the contact.
Forms
- Form submission completed: a form is submitted. Filter on the contact or on which form.
- Form submission approved: a submission that needed review is approved.
- Form submission rejected: a submission that needed review is rejected.
Purchases and visits
- Order created: an order is placed. Filter on the order, the contact, the business profile, or on any line item, which is how you start an automation for one product.
- Visit created: a visit is registered. Filter on the contact or the visit.
- Prepaid transaction created: a prepaid transaction happens. Filter on the contact or the transaction.
Bookings
Only there if your account uses bookings.
- Booking created: a booking is made.
- Booking updated: an existing booking changes.