Automation Event Triggers and Workflow Steps Explained
Automations in Oncord let you respond to customer activity without manual follow-up. Each automation starts with an event trigger and then
runs through one or more workflow steps.
This guide explains how automation event triggers work and outlines the available workflow steps, so you can build clear, predictable
automations that match your business processes.
Automation Event Triggers
An automation event trigger defines what causes an automation to start . Every automation must have one trigger, and it
always runs first.
To set up Automation Event Triggers:
Go to Dashboard > Marketing > Automation.
Click New Automation at the top of the page.
In the Automation Trigger section, click Select an event .
This opens the list of available event triggers. When you select an event:
The automation will run when that event occurs.
Additional settings may appear, depending on the trigger.
Below are the event triggers available on the Oncord Business plan. Select any trigger to view its details:
Cart - When a cart is abandoned
This trigger checks saved shopping carts once a day. It can enrol an identified contact whose cart falls within the selected time window and still contains eligible products.
The cart must be linked to a contact. Anonymous carts and carts created in the admin area are excluded. Empty carts, carts containing only deleted or unorderable products, and carts where the contact has purchased any of the eligible items within the past 90 days are also excluded.
Use Cases
Send a reminder email about items left in a cart.
Notify a sales or support team about incomplete checkouts.
Trigger After Number of Days
This setting selects a one-day window based on when the cart was last saved. At each daily check, Oncord selects carts saved after the cutoff the configured number of days ago, and up to and including the cutoff one day later.
For example, 1 day selects eligible carts saved since the previous day’s cutoff up to the current check. It can therefore trigger before a full 24 hours has elapsed. 3 days selects the window from three days ago to two days ago. The trigger does not wait for an exact number of elapsed hours or continually retry every older cart.
A contact can enter this automation at most once per day. Any email or SMS steps still apply their own recipient and send settings.
Sales - When a sale is made
This trigger runs when a sale is created in Oncord. A sale is recorded when a checkout is completed, regardless of whether the payment is
paid or unpaid, depending on your settings.
It’s commonly used to start post-purchase workflows, internal notifications, or follow-up actions linked to sales activity.
Use Case
Send an order confirmation or follow-up email.
Add contacts to a post-purchase group or workflow.
Notify staff when a sale meets certain criteria.
Trigger actions based on product type, order value, or payment status.
This trigger is often used with email, contact updates, group changes, or internal alerts.
Additional Options
For a sale with these attributes
These options let you control which sales will trigger the automation. The automation will only run if all selected conditions are
met.
Contains products
Choose which products must be included in the sale:
Any Product
From Specific Brands
From Specific Categories
Specific Products
Product Name Search
When you choose Specific Products and a selected product has order options, you can also choose which option value the sale must include, or Any .
Has payment status
Select whether the sale must be:
Dollar value of selected products
Filter sales based on the value of matching products:
Any Amount
At Least
Exactly
Less Than
Uses discount
Limit the automation to sales that used a particular discount:
No Discount Filter
Any of your discounts, listed by name
Shipping method
Limit the automation to sales with a particular shipping method:
Any
Any of your enabled shipping methods, listed by name
These filters allow you to target specific sales scenarios without creating multiple automations.
Sales - When a sale has been unpaid for a number of days
This trigger checks sales once a day. It selects sales whose sale date is exactly the configured number of calendar days before the check, whose payment status is Unpaid , and whose outstanding balance is at least 0.10.
The check uses the sale date, rather than the invoice due date or the exact time the sale was created. A matching sale must be linked to an existing contact. Matching sales are grouped by contact for the automation.
Use Cases
Send payment reminders a set number of days after the sale date.
Notify staff about unpaid sales.
Move matching contacts into a follow-up group.
Trigger for sales that have been unpaid for X days
Set the number of calendar days to look back from the daily check. For example, 30 days selects qualifying unpaid sales dated exactly 30 days earlier. The time of day on each sale is ignored.
The trigger does not run continuously when a sale reaches an elapsed-time threshold, or select all older unpaid sales. Enabling it will not automatically catch up sales already outside that matching date.
Sales - When a sale is fulfilled
This trigger runs when a sale’s fulfilment status is updated. It starts the automation when the sale reaches one or more selected fulfilment
states.
It’s useful for reacting to operational changes in the order lifecycle, such as shipping, pickup, or return handling.
Use Case
Send shipping or pickup confirmation emails.
Notify customers when an order has been packed or shipped.
Trigger internal alerts for fulfilment changes.
Start post-fulfilment workflows, such as review requests or follow-up messages.
This trigger is commonly used with customer notifications, internal updates, and post-delivery workflows.
Additional Options
When a sale fulfilment is updated to any of the following status
Select one or more fulfilment statuses. The
automation will run when a sale is updated to any selected status.
Available statuses include:
Not Picked Up
Picked Up
Unshipped
Printed
Packed
Shipped
Awaiting Return
On Hold
Back Ordered
Not Required
You can select multiple statuses to reuse a single automation across different fulfilment stages.
Sales - When a contact has credit expiring soon
This trigger runs when a contact has store credit that is approaching its expiry date. It allows you to start an automation before
the credit expires, giving the contact time to use it.
The automation runs once the credit reaches the configured number of days before expiry.
Use Case
Send reminder emails before store credit expires.
Notify contacts to return and complete a purchase.
This trigger is commonly used for customer reminders and re-engagement workflows.
Additional Options
Trigger X days before credit expires
Set how many days before the credit expiry date the automation should run.
The automation calculates the trigger date based on the credit expiry period.
The value must be less than or equal to the Credit Expiry Days setting in Commerce Configuration .
For example, if credits expire after 30 days and this is set to 7 days , the automation will run 23
days after the credit is created ,
sending the notification 7 days before expiry.
Contacts - When a contact is created
This trigger runs when a new contact is created in Oncord.
It applies to contacts added through any source, including forms, manual entry, or imports.
Use Case
Send a welcome or onboarding email.
Add new contacts to a group.
This trigger is commonly used for onboarding and lead management.
Contacts - When a field is changed
This trigger runs when a specific field on a contact record is updated.
You can choose which contact field should trigger the automation, such as email address, name, address details, communication preferences,
or system fields like updated date.
By default, the trigger runs only when an existing contact’s field changes. You can optionally allow new contacts to trigger the automation
as well.
Use Case
Send a confirmation email when a contact updates their email address.
Apply group changes when a contact’s status or type changes.
Start a workflow when a contact opts out of communications or changes preferences.
This trigger is commonly used with email steps, contact updates, and group management etc.
Additional Options
Which field triggers the event
Select the contact field to monitor. The automation will run only when this specific field changes.
Available fields include system fields (such as created or updated datetime), identity fields (email, username), communication settings, and
standard contact profile fields.
Trigger event on new contacts
Enable this option to allow the automation to run when a new contact is created and the selected field is set for the first time.
If disabled, the automation will run only when the field changes on existing contacts.
Contacts - On or before birthdays
This trigger runs based on a contact’s date of birth. The automation starts on the contact’s birthday or a specified number of days before
it.
This allows you to run birthday-related workflows without manual scheduling or recurring campaigns.
The trigger uses the contact’s Date of Birth field. Contacts without a date of birth will not trigger the automation.
Use Case
Send birthday or pre-birthday emails or messages.
Offer time-based promotions tied to a contact’s birthday.
Add contacts to a temporary birthday group for targeted follow-ups.
Additional Options
Trigger days prior to the birthday
Set how many days before the birthday the automation should run.
A value of 0 triggers the automation on the birthday itself.
A positive number triggers the automation that many days before the birthday.
This allows you to run workflows in advance, such as sending early offers or reminders.
Send spreadsheet of birthdays to admin
Optionally send a spreadsheet of upcoming birthdays to administrators on a defined schedule:
Every day
Every week
Every month
Contacts - On or before a custom field date
This trigger runs based on a date stored in a contact custom field, such as a renewal, expiry or anniversary date. The automation starts on that date or a specified number of days before it.
This trigger appears only when your contacts have at least one custom field of the Date or Date with Time type. To add one, see Managing Contact Custom Fields .
Oncord checks the dates once a day. Each contact enters the automation once per date, so if the date in the field changes, the automation can run again for the new date.
Use Case
Send a renewal reminder before a membership or subscription date.
Remind a contact before a licence, certificate or registration expires.
Follow up on an anniversary or service date.
Additional Options
Which Custom Field?
Select the date field to use.
Trigger this ... days prior to the (field name)
Set how many days before the date the automation should run. A value of 0 triggers the automation on the date itself.
Also send spreadsheet to admin
Optionally e-mail a spreadsheet of upcoming dates to the addresses you enter:
Every day
Every week
Every month
Groups - When someone is added to a group
This trigger runs when a contact is added to a selected group.
The automation will only run for the groups you select in the trigger configuration.
Use Case
Send a welcome or onboarding email when a contact joins a group.
Start a follow-up workflow after a lead is added to a specific group.
This trigger is commonly used with email steps, contact updates, and group management.
Additional Options
Which groups should trigger this event
Select one or more groups that should activate the automation.
The automation will run only when a contact is added to any of the selected groups.
Groups - When someone is removed from a group
This trigger runs when a contact is removed from a selected group.
The automation will only run for the groups you select.
Use Case
Send a follow-up or exit email when a contact leaves a group.
Move contacts into a different workflow or group.
Update contact records based on lifecycle changes.
Additional Options
Which groups should trigger this event
Select one or more groups that should activate the automation.
The automation will run only when a contact is removed from any of the selected groups.
Analytics - When someone visits a page
This trigger runs when a contact visits a selected page on your website. The automation starts as soon as the page view is recorded.
This automation can fire at most once, ever, per contact, not once per session or once per day.
You can choose which pages should trigger the event. The automation will run only when one of those pages is visited. This allows you to
react to specific content views rather than all site activity.
Page visits are tracked through Oncord analytics. The trigger runs only for identifiable contacts.
Use Case
Start a follow-up workflow when a contact views a key landing page.
Add contacts to groups based on content interest.
Trigger targeted emails after pricing or product page views.
Additional Options
What pages trigger this event?
Search for and select one or more pages.
The automation will run only when a contact visits any of the selected pages.
Forms - When a form is submitted
This trigger runs when a selected form is submitted. The automation starts immediately after the submission is received.
You can choose which forms should trigger the automation. The trigger applies to submissions from website forms.
This allows you to react to specific form activity rather than all form submissions.
Use Case
Send a confirmation or follow-up email after a form is submitted.
Notify staff when a lead or application form is received.
Add contacts to groups based on the form they submitted.
Start onboarding or review workflows tied to specific forms.
This trigger is commonly used with email steps, group updates, contact updates, or internal notifications.
Additional Options
Which Forms?
Select one or more forms that should activate the automation.
The automation will run only when any of the selected forms are submitted.
And Submission Meets Conditions
Optionally, limit the automation to submissions with particular answers. This appears once you select a form.
Click + Add a Submission Condition .
Choose a form field, a comparison (such as Equals or Contains ) and a value.
If you add more than one condition, choose whether the form must match all or at least one of them.
Forms - When a form's workflow status is changed
This trigger runs when a submission’s workflow status changes for a selected form. The automation starts as soon as the submission moves
into the chosen workflow step.
Form workflow statuses are typically updated by staff during review processes, such as approving or rejecting a submission. This trigger
allows automations to respond to those decisions without manual follow-up.
The automation will run only for the selected form and workflow status.
Use Case
Send an approval or rejection email when a form is reviewed.
Notify staff when a submission reaches a specific review stage.
Start onboarding workflows after an application is approved.
Apply contact or group updates based on form outcomes.
Additional Options
Which Form
Select the form whose workflow status should be monitored.
When Changed to Workflow Step
Choose the workflow step that should trigger the automation, such as Pending , Approved , or Rejected .
The automation will run only when a submission enters the selected step.
Events and Cliniko Triggers
These triggers appear when the matching feature or app is set up.
When the Events Management feature is installed:
Events - When an event is about to start
Events - When an event ends
Events - When someone is added to an event
Events - Remind someone to RSVP or attend an event
For details, see Event Automation Triggers .
When the Cliniko app is connected:
Cliniko - On an upcoming appointment
Cliniko - When a contact cancels their appointment
Cliniko - When a contact did not arrive to an appointment
Cliniko - When a contact finishes their appointment
Cliniko - When an appointment is created
For details, see Setup the Cliniko Integration .
Workflow Steps
Workflow steps define what happens after an automation is triggered. Each step performs a specific action, such as sending a message,
updating a contact, or waiting before continuing.
You can combine multiple steps to create structured workflows that respond to contact behaviour, sales activity, or internal processes in a
controlled way.
Below are the workflow steps available on the Oncord Business plan. Select any step to view its details.
Tasks - Create a Task from a Saved Task
This workflow step creates a task on a contact record using a predefined saved task .
It’s usually used to automatically assign reminders to administrators when an automation runs.
What is an Oncord Task?
An Oncord Task is a reminder linked to a contact record.
Tasks are typically used to prompt follow-up actions, such as calling a contact, reviewing a submission, or checking in after a sale.
For a full overview of creating and managing tasks, see Setting
Tasks .
How it Works?
When this step runs, Oncord creates a new task on the triggered contact using a selected saved task template.
How to Configure This Step
In the workflow step settings:
Select a Saved Task to use.
Select one or more admin contacts.
These administrators will be responsible for the task. At least one admin must be selected.
When the automation reaches this step:
The task is created on the contact record.
The selected administrators receive the task reminder.
Use Cases
Create a follow-up call task after a form submission.
Assign a sales follow-up when a high-value sale is created.
Notify support staff to review an application after approval.
Groups - Add Contact to Groups
This workflow step adds a contact to one or more selected groups when the automation runs.
For more details about creating and managing groups, see Managing
Groups .
How to Configure This Step
In the workflow step settings:
Select one or more groups
These are the groups the contact will be added to.
When the automation reaches this step:
The contact is added to the selected groups.
Use Cases
Add new leads to a Leads group after a form submission.
Add contacts to a VIP or Priority group based on order value.
Groups - Remove Contact from Groups
This workflow step removes a contact from one or more selected groups when the automation runs.
How to Configure This Step
In the workflow step settings:
Select one or more groups
These are the groups the contact will be removed from.
When the automation reaches this step:
The contact is removed from the selected groups.
Use Cases
Remove contacts from a Leads group after conversion.
Move contacts out of onboarding or trial groups.
Update group membership based on form outcomes or sales activity.
Send E-mail to Customer
This workflow step sends an email message to the contact when the automation reaches this step.
It’s one of the most commonly used workflow steps and is typically used for confirmations, follow-ups, onboarding, and notifications.
How to Configure This Step
In the workflow step settings:
Select a pre-created email message , or click Create New Message to create a new one.
Choose Live Mode or Test Mode
Test Mode sends the email only to a specified test address.
Live Mode sends the email to the contact when the automation runs.
Optionally tick Send to 'Pending' contacts and / or Send to 'Unsubscribed' contacts
By default this step only emails subscribed contacts. Tick these options when the message must reach everyone regardless of their
marketing preferences, such as an order or booking confirmation. A warning appears below the options when you tick either one, because
sending commercial email to contacts who have not opted in may breach spam laws.
For more details and examples, see Setup Your First E-mail Automation .
Subscription Status
Oncord checks each contact's subscription status before sending automated emails. By default, messages are only delivered to contacts who have
consented to receive them:
Subscribed — these contacts will receive automated email messages.
Pending — these contacts have not explicitly opted-in. They are skipped unless Send to 'Pending' contacts is ticked on the step.
Unsubscribed — these contacts have opted-out. They are skipped unless Send to 'Unsubscribed' contacts is ticked on the step.
These options belong to the workflow step rather than the email message, so the same message can reach every contact in one automation
(for example a receipt) while another automation that sends it only reaches subscribed contacts. Previously they were set on the email
message's Settings page; existing automations keep the behaviour they had. When a contact is skipped, the automation's
history records that the email was not sent because of their subscription status.
For more details, see Managing Subscribers .
Use Cases
Send a welcome email after a contact is created or added to a group.
Send confirmation emails after form submissions.
Trigger follow-up emails after a sale or checkout.
Send reminder or notification emails based on contact activity or timing.
Send SMS to Customer
This step attempts to send the selected SMS when the contact reaches it, subject to the step’s recipient settings and account requirements.
How to Configure This Step
Select an existing automation SMS message, or click Create New SMS .
Choose Test Mode to send to the specified test number, or Live Mode to send to the contact’s mobile number.
Optionally tick Send to 'Pending' contacts and / or Send to 'Unsubscribed' contacts . By default this step only sends to subscribed contacts. A warning appears when you tick either option, because sending commercial SMS to contacts who have not opted in may breach spam laws.
To change the message, select it and click Edit Message .
Subscription Status
Subscribed: Eligible by default, subject to SMS opt-out and the other send requirements.
Pending: Excluded unless Send to 'Pending' contacts is ticked on the step.
Unsubscribed: Excluded unless Send to 'Unsubscribed' contacts is ticked on the step.
These options belong to the workflow step rather than the SMS message, so the same message can be handled differently in another automation.
Send to 'Unsubscribed' contacts also bypasses the contact’s SMS opt-out check. Subscription and opt-out checks apply in Test Mode too, so a contact who fails those checks will not produce a test send.
Live sends require a valid mobile number, an active SMS gateway and an account permitted to send SMS. A contact’s subscription status alone does not guarantee delivery.
See SMS Marketing and Managing Subscribers for related guidance.
Use Cases
Notify customers about order updates or pickups.
Send short follow-up messages after form submissions.
Test Conditions
This workflow step checks whether a contact meets one or more conditions before continuing through the workflow.
It’s used to control flow, ensuring that only contacts matching specific criteria proceed to the next step.
How it Works?
When this step runs, Oncord evaluates the configured conditions against the triggered contact.
If the conditions are met, the workflow continues.
If the conditions are not met, the workflow stops at this step.
How to Configure This Step
In the workflow step settings:
Click the condition field to select a condition.
Configure the condition options.
Additional fields will display depending on the condition selected.
Click the blank space to add another condition.
By default, conditions are joined using AND .
Click AND to change it to OR if required.
Click the “=” icon on a condition to negate it
This changes the logic to is not , excluding matching values.
You can add multiple conditions to build simple or complex logic.
Use Cases
Continue only if a contact belongs to a specific group.
Exclude contacts who have already submitted a form.
Target contacts based on page visits or purchase history.
Wait...
This workflow step pauses the automation for a defined period of time before continuing to the next step.
It’s used to control timing, space out messages, or delay actions until a specific day or time.
How it Works?
When this step runs, the automation pauses for the configured duration.
Once the wait period has completed, the workflow continues to the next step based on the selected timing rules.
How to Configure This Step
In the workflow step settings:
Set the wait duration
Choose a number and a time unit (minutes, hours, days, weeks, or months).
For days, weeks or months, click Run at a Specific Time to choose a time for the next step. Weeks and months also let you choose a day of the week.
Use cases
Delay follow-up emails after a form submission.
Wait a set number of days before sending reminders.
Space out multi-step onboarding or nurture workflows.
Trigger Webhook
This workflow step sends information to another system by calling a webhook you've set up in Oncord, such as passing a new contact or a form submission to an external service.
You create webhooks in Dashboard > Settings > Developer > Webhooks . For the full steps, see Webhooks .
How to Configure This Step
In the workflow step settings:
Select a webhook in Select Webhook , or click Create new webhook .
If the webhook has a test URL, choose Live or Test under Environment .
Under Payload Fields , enter a value or insert a variable for each field. A blank field uses the field's default value.
If the webhook is disabled, this step doesn't send anything. Tick Enable this webhook on the webhook to turn it on.
Use Cases
Send new form submissions to another business system.
Notify an external service when a sale is made.
Events - Add Attendee to Events
This workflow step adds the contact to an event as an attendee. It appears when the Events Management feature is installed.
How to Configure This Step
In the workflow step settings:
Select the event in Add attendee to current event .
Choose a status in With RSVP status of : Attending , Not Attending , Maybe Attending or No RSVP . Maybe Attending appears when the event allows it.
If the contact is already an attendee of the event, their RSVP status is updated.
Use Cases
Add contacts to an event after they submit a registration form.
Add new members to an induction or welcome event.
Recurring Sales - Mark as Terminated
This workflow step terminates the contact's recurring sale plans. It appears when the Recurring Sales feature is installed.
How to Configure This Step
In the workflow step settings:
In Select recurring sales to terminate , choose All Recurring Sales or Recurring Sales Containing Products .
If you chose Recurring Sales Containing Products , search for the products and add them.
This step doesn't start automations that use the Recurring Sales - When a recurring sale plan is terminated trigger.
Use Cases
End a contact's plans when they are moved to a cancelled or inactive group.
Affiliates - Create an affiliate
This workflow step creates an affiliate for the contact, so they can refer visitors and earn commission. It appears when the Affiliates feature is installed. For more about affiliates, see Setup Affiliates .
How to Configure This Step
In the workflow step settings:
Under Visitor Commission , enter the Commission per visit and Commission per registration .
Under Sale Items Commission , enter the Base commission per item and Plus percentage commission .
In Affiliations last for , choose The length of the visitor's session , A specified number of days or Forever while registered as a contact .
Tick Affiliate Existing Contacts to create an affiliation when a visitor who is already a contact clicks through.
If the contact is linked to a company as an employee, the affiliate is created for the company, with the contact as its administrator. The step creates a new affiliate each time it runs, so use it with a trigger that runs once per contact.
Use Cases
Create an affiliate when someone submits a partner or referral program application form.