Create and organize rules

Step by step

1. Open Tools → Automation. The menu says Automation, although the system generally calls it workflow.
2. Click New rule. The wizard opens in two columns.
3. Enter Rule name (optional) at the top and leave the adjacent toggle at Rule is inactive. You will test it on an existing object before enabling it (Events — what starts a rule); see below.
4. In Trigger, select an event from Select event... (Events — what starts a rule). If you change to an event from another area, the Change trigger domain? dialog appears. Change and clear removes conditions and actions that do not match.
5. For a status change, an additional Trigger on status (pre-filter) field appears. This is a cheaper filter than a condition and is checked first.
6. Add conditions in Conditions with Add condition. The heading reminds you that all must be met (Workflow conditions — every listed condition must be met).
7. Add actions in the Action column with Add action. Until you select an event, it says Select a trigger first to add actions. (Actions — what a rule can do).
8. Expand Advanced and check Log unmet conditions. It is enabled by default for new rules; without it, history hides runs rejected by conditions. Consider Run once too.
9. Read the sentence assembled at the bottom and click Save (or Save changes when editing). Missing fields produce Select an event!, Add at least one action!, or Complete or remove incomplete action fields.
10. If a dialog asks for a 2FA code, enter it (2FA confirmation when changing permissions).
11. Read the message after saving. It usually confirms the save, but may be yellow if the rule closes a loop with another rule or if two rules write different values to the same field (Automation pitfalls). The save is not blocked.
12. Watch Runs (24h) in the rule list and open history to see what the rule actually did (Execution history — what really happened).
13. Enable the rule with its list-row toggle only after it behaves correctly. Rule enabled. confirms the change.

The wizard

The wizard opens as a two-column panel: event and conditions on the left, actions on the right. A sentence describing the rule appears at the bottom; read it before saving.

Events are grouped by area. Choosing one limits the available conditions and actions to that area (Automations — WHEN, IF, THEN).

Advanced has two options:

• Run once — the rule will not run a second time for the same object. Its tooltip says Prevents repeated execution.
• Log unmet conditions — history also records runs rejected by conditions. This is very useful when tuning a new rule, so new rules have it on by default (older rules retain their setting). It also gives the rule 14-day history retention.

Test a rule on an existing object

The Test rule button (flask icon) on the rule row checks its conditions against an existing object. Enter its number, for example an order ID, and click Run test.

The test does not execute anything: no action runs, no history entry is created and nothing is sent to the marketplace. It shows:

• Each condition separately — whether it passed and with what value.
• Conditions not checked — after the first failed condition the rule would stop, so remaining ones are greyed out instead of being presented as checked.
• Actions that would run, in order.
• Gates beside the conditions — whether the rule is enabled, waiting for a specific status, and whether Run once has already run for this object.

You can test a disabled or managed rule (with a lock) too, to find out why it did not run.

What the test cannot tell you

It checks conditions, not effects. Whether an action succeeds — for example, whether a marketplace accepts a status or a courier issues a label — is known only when the rule runs for real.

Use the same safe procedure:

1. Build the rule disabled.
2. Test it on several existing objects: one that should match and one that should not.
3. Keep Log unmet conditions enabled; it is on by default for new rules.
4. Start with the least irreversible action, such as a notification only.
5. Enable the rule and watch its history (Execution history — what really happened).
6. Add data-changing actions only after that.

Take special care with actions that send data to a marketplace or create shipments; they cannot be undone with one click.

Enable and disable

Use the toggle beside the rule in the list or in the wizard header. Disabling takes effect immediately for new events.

Deleting is a separate Delete action, confirmed in the Confirm deletion dialog. Every change requires 2FA confirmation (2FA confirmation when changing permissions).

Order

Rules run in the order shown in the list. Drag them or use Move up and Move down in the row. The column is Execution order.

Keep in mind:

• Order matters only between rules for the same event. Different events never compete with one another.
• Dragging reorders the entire area, but in a filtered or paginated list you can move only the rules currently shown.

Rule counters

Runs (24h) shows the number of runs and success rate over the last day, with a link to history filtered to that rule. It is the quickest way to tell whether a new rule fires at all.

Managed rules

Rules with a lock icon were created from a setting, not manually: an integration toggle for sending a status, invoice or tracking number to a marketplace, or the Buyer emails toggles in customer order page settings (the name starts with Buyer e-mail: order page link). You cannot edit, disable or delete them; change the underlying setting instead. An edit attempt shows where that setting is.

History retention

Rule history is cleaned once per day. You cannot change its retention period in this form; contact NOXTI support to request a change (Execution history — what really happened).

Events — what starts a rule