Multi-Step Automation Workflows
Every action in an automation rule runs in the order you define it. By default each action is independent, but you can give any action an Action ID so that subsequent actions can reference its output.
How it works
- Add an action (e.g. Create Product).
- In the action's settings, assign an Action ID — a short label you choose, for example
new_product. - In any action that comes after it, use
{{ new_product.field }}placeholders to pull values from that result.
Actions still execute sequentially. If an earlier action fails, subsequent actions in the chain do not run.
Example — create a product and email the team with the new SKU
Use case: when SKU mapping fails, auto-create the product and immediately notify the inventory team with the new product's details.
| Step | Action | Action ID |
|---|---|---|
| 1 | Create Product | new_product |
| 2 | Send Enhanced Email | (none needed) |
In the Enhanced Email body:
A new product was automatically created.
SKU: {{ new_product.sku }}
Product ID: {{ new_product.id }}
Please review and update details as needed.
Tips
- Action IDs are optional. Only add one when a later action genuinely needs the result.
- Any action can have an Action ID — tag assignments, field updates, external API calls, etc. Typically the most useful ones are actions that create something (product, assembly order) whose identity you need downstream.
- Placeholders follow the same syntax as Enhanced Email and Update Column dynamic values (see How do I write dynamic values and date calculations in automation field-update actions?).
- Testing: Use the Sales Orders grid → Actions → Bulk Actions → Trigger: Order Created / Updated to replay the rule on a real order without waiting for a live event. See How to Manually Trigger Automations for Orders.