Automations — WHEN, IF, THEN
A rule is one sentence: when something happens, if the conditions are met, then do these actions. Three parts, in that order.
An automation rule is a sentence with three parts:
WHEN (event) → IF (conditions) → THEN (actions)
The builder follows this order and reads like a sentence.
| Part | Number | Meaning |
|---|---|---|
| WHEN | exactly one | Event that triggers the rule (Events — what starts a rule) |
| IF | zero or more | Conditions — all must be met (Workflow conditions — every listed condition must be met) |
| THEN | one or more | Actions performed in order (Actions — what a rule can do) |
A rule belongs to a domain
The event determines the domain; you do not select it separately: orders, products, documents, returns, consolidated parcels, or warehouse.
Available conditions and actions are limited to the event's domain. A rule starting with a product event will not offer an order action. Changing the event to another domain clears incompatible rows after confirmation.
Some actions work across domains, including notifications and calling a custom event.
Where to find it
Go to Tools → Automation. Three related screens are available:
- Rules list — create, enable, and organize rules (Create and organize rules).
- Custom events — buttons that trigger rules manually (Custom events — manually triggered buttons).
- Automation logs — under Advanced (Execution history — what really happened).
The area has its own Automation module permission (previously shared with Settings; existing grants were migrated). Each change also requires 2FA confirmation (2FA confirmation when changing permissions).
Before you build your first rule
- You can test a rule, but cannot run it “dry”. Test rule checks conditions on an existing object and performs no actions. A saved and enabled rule runs in production. Build it disabled, test it, then deliberately enable it (Create and organize rules).
- Rules run in the background, not instantly. Execution goes through a queue (How a rule runs — queue, retries and waiting).
- Some actions do nothing despite a successful result. Read Automation pitfalls before relying on one in a process.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo