Skip to main content
Every automation starts with a trigger — the event that sets it off. You can then add conditions to narrow it down, so the automation only fires when specific criteria are met.

​
Triggers

There are three triggers, available for both Orders and Events:
TriggerWhen it fires
CreatedWhen a new order or event is first created
Status changedWhen the status of an order or event changes (e.g. from Unconfirmed to Confirmed, or from Confirmed to Picked)
Payment status changedWhen the payment status changes (e.g. from Unpaid to Paid, or from Paid to Refunded)
The status changed and payment status changed triggers fire every time the status changes, not just once. If an order goes from Unconfirmed → Confirmed → Picked, the automation is evaluated at each step. Use conditions to target a specific status.

​
Order triggers

For order automations, the statuses that can trigger a status change include:
  • Unconfirmed, Confirmed, Picked, Ready for Fulfilment, With Courier, Out for Delivery, Fulfilled, Cancelled
Payment statuses include:
  • Unpaid, Partially Paid, Paid, Over Paid, Refunded, Partially Refunded, Void, Expired

​
Event triggers

For event automations, the statuses that can trigger a status change include:
  • Draft, Quote Sent, Follow Up, Quote Accepted, Order Finalisation, Order Created, Completed, Cancelled, Archived
Payment statuses follow the same set as orders.

​
Conditions

Conditions let you filter when an automation fires. You can add one or more conditions, and all of them must be true for the automation to run. Each condition has three parts:
  1. Field — what you’re checking
  2. Operator — how you’re comparing it
  3. Value — what you’re comparing it to

​
Condition fields for Orders

FieldWhat it checksExample use
Order typeThe type of order (e.g. Gift, Funeral, Corporate, Event)Only fire for funeral orders
Fulfilment methodHow the order is being fulfilled — Delivery, Collection, or RelayOnly fire for delivery orders
Payment statusThe current payment status of the orderOnly fire when the order is fully paid
AccountThe customer account linked to the orderOnly fire for orders from a specific trade account

​
Condition fields for Events

FieldWhat it checksExample use
StatusThe current status of the eventOnly fire when the event is confirmed
Payment statusThe current payment statusOnly fire when a deposit has been received
AccountThe customer account linked to the eventOnly fire for a specific corporate client
Event typeThe category of event (e.g. Wedding, Funeral, Corporate)Only fire for wedding events

​
Operators

OperatorWhat it means
EqualsThe field must match the value exactly
Not equalsThe field must not match the value
Greater thanThe field must be greater than the value (for numeric fields)
Less thanThe field must be less than the value (for numeric fields)

​
Multiple conditions

When you add multiple conditions, they work with AND logic — every condition must be true for the automation to fire. For example, if you set:
  • Fulfilment method equals Delivery
  • Payment status equals Paid
The automation will only fire for delivery orders that are fully paid. It won’t fire for collection orders, and it won’t fire for unpaid delivery orders.
If you need “or” logic (e.g. fire for delivery OR collection orders), create two separate automations with the same action — one for each condition.

​
Putting it together

Here’s how a complete trigger + condition setup might look: “Send a confirmation email when a delivery order is paid”
PartSetting
ModelOrder
TriggerPayment status changed
Condition 1Fulfilment method equals Delivery
Condition 2Payment status equals Paid
ActionSend email
This automation fires every time an order’s payment status changes, but only runs the action if the order is a delivery order AND it’s now fully paid.

​
Common questions

Yes. Use the status changed trigger combined with a condition that checks for the specific status. For example: trigger = “status changed”, condition = “status equals Confirmed”.
Yes. A POS sale creates an order, so it will trigger any “order created” automations.
No. Every automation needs a trigger. Conditions only filter when that trigger fires — they can’t fire an automation on their own.
The automation simply doesn’t run. Nothing happens, and nothing is logged as a failure — it’s treated as “not applicable”.

​
What’s next?

Actions

Set up what happens when your automation fires.

Automations Overview

Back to the main automations guide.
Last modified on March 11, 2026