The following article provides an explanation of the various triggers, criteria and actions that are available to use when setting up automation workflows.
What are Triggers?
A trigger defines the criteria which causes the automation to begin. Think of triggers as "wait until this happens". If our trigger is "Contact Added", the automation will begin as soon as a contact has been added into the database.
Every trigger supports a filter to allow you to limit execution to a certain timeframe. As an example, if you are running a competition for the month of July, you may setup an automation to manage the competition and set the Trigger to only execute between 1st July - 31st July.
Available list of triggers and definitions:
|Contact Added||When a new contact has been added into the database. If an existing contact is re-added, it will not execute this trigger. Only contacts that have never been previously added into the database will cause the trigger to execute.|
|Contact Updated||When the details of an existing contact have changed.
As part of this step, you can also specify which specific contact field needs to be updated in order to satisfy the conditions of this trigger.
|Contact Deleted||Triggers the automation whenever a contact has been deleted from the database.|
|Contact Note Added||A new note/reminder has been added against a contact. This action can be performed via the View/Edit Contact page or through the API.|
|Contact Note Deleted||An existing note/reminder has been deleted from a contact.|
|Campaign Sent||A campaign (email or sms) has been sent. This trigger also provides the option to filter the sent campaign to a specific Campaign Folder. If you have selected a campaign folder, the trigger will only execute when a campaign part of the selected folder has been sent out.|
|Campaign Reply||A reply has been received on a previously sent campaign. Replies will only be received for campaigns that were sent with the "Allow Replies" setting selected. This is supported for both Email & SMS.|
|Email Sent||Same as "Campaign Sent" trigger but, specific to Email only|
|Email Reply||Same as "Campaign Reply" trigger but, specific to Email only|
|Email Opened||Triggers whenever a contact opens an email that was previously sent to them. The trigger provides an option of specifying a campaign folder. If selected, only emails opened that are within the specified campaign folder will cause the trigger to execute.|
|Email Clicked||Triggers whenever a contact clicks a link inside an email that was previously sent to them. The trigger provides an option of specifying a campaign folder. If selected, only emails opened that are within the specified campaign folder will cause the trigger to execute.
Another option of specifying the exact URL can also be specified. The trigger will only execute when a contact clicks a link that hyperlinks to the provided URL.
|Email Bounced||A campaign sent to a contact has bounced back. The trigger provides an option of specifying a campaign folder. If selected, only bounces to emails sent that are within the specified campaign folder will cause the trigger to execute.
A common use for this trigger is to setup an automation to send an SMS to a contact with a link to an "update details" form whenever an email has bounced back.
|Email Optout||Contact has unsubscribed via an email previously sent to them.|
|SMS Sent||Same as "Campaign Sent" trigger but, specific to SMS only|
|SMS Delivered||Same as "Campaign Sent" trigger but, specific to SMS only. Will only execute when a delivery receipt has been received confirming the message was successfully delivered.|
|SMS Reply||Same as "Campaign Reply" trigger but, specific to SMS only|
|SMS Optout||Contact has unsubscribed via an sms previously sent to them.|
|Webform Submitted||A form has been submitted by the contact. This trigger provides the option of specifying a specific form that must be submitted in order to execute the automation. A common example usage of this trigger is to setup an automated email whenever a form has been submitted.|
|Webhook Received||Data has been received via a webhook. The trigger will provide you with a Webhook URL specific to the automation and provide security options for transmission.
All data pushed to the webhook must comply with the /contacts endpoint of the API.
|Day / Time||A non-event based trigger. Allows you to dates, times & schedules that cause the automation to execute (eg: Every Monday at 9am, Daily at 2pm, on the 1st of each month at 3pm etc...).
Important Note: This trigger will select the whole database. Ensure you are using Criteria blocks to filter the list of Contacts to only those that should have actions performed against them.
|Purchase Added||A transaction has been recorded against a contact. Transactions can be added via various integrations and will contain a list of items purchased and amount spent by a contact.|
|Purchase Updated||A transaction previously connected to a contact has been updated. This trigger will only execute if an existing transaction has been modified.|
|Purchase Deleted||A transaction has been removed & deleted|
|Visit Added||Booking/Reservation has been recorded against a contact. Data is added via various integrations with reservation & wifi platforms. Visits record the date, time, location & pax for each contact.
A common use of this trigger is to send a confirmation email when a booking has been made by a contact.
|Visit Updated||An existing reservation/booking has been updated.|
|Visit Deleted||A reservation/booking has been deleted.|
|Voucher Assigned||A voucher/offer has been assigned to a contact. This trigger works alongside the "Vouchers & Offers" functionality that can be found within the Apps section of the platform.
The trigger will execute whenever a voucher has been allocated to a contact (generally via an email or sms sent to them with a unique code).
|Voucher Redeemed||A previously assigned voucher has been redeemed by the contact. Redemption data is captured via the API.
Not all integrations provide redemption data. Get in touch with our support team to confirm.
Article is closed for comments.