Create an automation
Automations
Create an automation
Create a new automation rule with its conditions and actions.
POST
Create an automation
Request Structure
Key Fields
| Field | Required | Description |
|---|---|---|
resource_name | Yes | Triggering resource |
event | Yes | Triggering event (depends on resource_name) |
enabled | Yes | Whether the automation is active |
conditions_changes | Yes | Conditions to add — only type: ADD is valid on create |
actions_changes | Yes | Actions (and parameters) to add — only type: ADD is valid on create |
Conditions, Actions & Parameters
Conditions, actions, and action parameters are managed inline through this payload using change objects. On create onlyADD is allowed; the update endpoint also accepts UPDATE and DESTROY (which require the existing record id).
Resource Events
| resource_name | events |
|---|---|
goods_out | created, completed, updated, processed, cancelled |
goods_in | completed, created, cancelled, moved_to_part |
goods_out_pick_list | completed, created, cancelled, picked |
invoice | submitted, authorised, paid |
load_drop | dispatched |
stock_balance | updated |
stock | positively_adjusted, negatively_adjusted, placed_on_hold, released_from_hold, received, unreceived, dispatched, undispatched, account_transferred, picked |
putaway_task | completed |
failure_event_log | created |
ftp_file | uploaded |
ftp_import | failed |
daily_schedule / weekly_schedule / monthly_schedule / one_time_schedule | triggered |
Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Body
application/json
Response
Automation created successfully

