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.
This page covers features gated by Admin-tier permissions — typically Settings access. Admins have these by default; your administrator can adjust who has them in Settings > Team.

​
Triggers

There are three triggers, available for both Orders and Events.

​
Status changed and payment status changed

For these two triggers, you pick the target status on the trigger itself — the automation only fires when the order or event lands on that status. You don’t add a separate condition for the status. For example, “Order → Status changed → Confirmed” fires only when an order moves into Confirmed. Earlier or later transitions are ignored.

​
Order statuses

For order automations, you can target statuses including Unconfirmed, Confirmed, Order picked, Ready for fulfilment, With courier, Out for delivery, Fulfilled, and Cancelled.

​
Event statuses

For event automations, you can target statuses including Draft, Quote sent, Follow up, Quote accepted, Order finalisation, Order created, Completed, Cancelled, and Archived.

​
Payment statuses

For Orders or Events, you can target payment statuses including Unpaid, Partially paid, Paid, Over paid, Refunded, Partially refunded, Void, and Expired.

​
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

​
Condition fields for Events

Account is a yes/no field — it asks whether the order or event is tied to an account customer, not which specific account. Pick Equals true or Equals false.

​
Operators

In practice, every condition field listed above only offers Equals and Not equals. Numeric operators exist in the data model but aren’t exposed for any of the current condition 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” The trigger itself targets Paid, so the automation only runs when an order’s payment status lands on Paid. The condition then narrows that further to delivery orders.

​
Common questions

Yes. Choose the Status changed (or Payment status changed) trigger and pick the target status from the dropdown next to it. The automation then fires only when the record lands on that status.
Yes. A POS sale creates an order, so it triggers any “order is 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 doesn’t run. Nothing happens, and nothing is logged as a failure — it’s treated as not applicable.
No. Automations only trigger on orders and events. Task creation, completion, and assignment don’t fire automations.

​
What’s next?

Actions

Set up what happens when your automation fires.

Automations Overview

Back to the main automations guide.
Last modified on June 2, 2026