Automation Editor
The automation editor (/automations/:id) is a visual tool that lets you design complex workflows by connecting trigger and action nodes. Each node represents a step in your automation.
Editor Interface
The editor presents a visual canvas where you can drag and connect nodes to build your flow:
Node Types
| Node | Function | Example |
|---|---|---|
| Trigger | Starting point of the flow | Order created, customer registered |
| Condition | Evaluates a rule before continuing | If total > $500 |
| Action | Executes a task | Send email, update tag |
Node Composition
Nodes connect in sequence by dragging from one node's output to the next node's input. You can create branches using condition nodes to execute different actions based on the result.
Execution order
Actions execute top to bottom following the connections. If an action fails, subsequent actions in the chain will not run.
Available Triggers
Triggers are grouped by domain:
- Orders: Created, updated, cancelled, paid, shipped.
- Products: Created, updated, deleted, synced.
- Inventory: Updated, depleted, restocked.
- Customers: Registered, updated, first purchase.
Available Actions
- Send email notification
- Send message (WhatsApp, SMS)
- Tag order or customer
- Update custom field
- Create internal task
- Call external webhook
Publish and Unpublish
In the top corner of the editor you will find a toggle to control the publication state:
- Published: The automation is active and runs in real time.
- Draft: The automation is deactivated and does not respond to events.
Tip
Use draft state while designing your flow. Only publish when you are confident the configuration is correct.
Test Trigger
The Test trigger button simulates the configured event to verify your automation works correctly without waiting for the real event to occur.
Configure test data
The editor generates sample data based on the selected trigger type.
Run test
Click Test trigger to simulate the full flow execution.
Verify result
Check the execution history to confirm each action completed successfully.
Execution History
The Runs tab (/automations/:id/runs) shows the log of every time the automation has fired:
| Status | Meaning |
|---|---|
| Pending | The execution is queued waiting for processing |
| Running | Actions are currently being executed |
| Completed | All actions finished successfully |
| Failed | One or more actions encountered an error |
Each execution shows total duration and details for every step, allowing you to diagnose issues quickly.
Failed executions
Review failed executions regularly. A pattern of failures may indicate a configuration issue with the trigger or actions.
Best Practices
- Name your automations descriptively (e.g. "Notify team - high value order").
- Always test before publishing using the test button.
- Review execution history periodically to detect errors.
- Archive automations you no longer need instead of deleting them.
Next Steps
- Automations overview — Return to the list and automation management
- Managing orders — Configure triggers based on orders
Need help? Contact support or check our FAQ.