set_automation_status
Sets the status to draft, active or paused. Active needs automations:run; draft is refused once the automation was active, because it would remove waiting messages (use paused). Templates not approved yet are listed in notices.
| Tool name | set_automation_status |
| Permission | automations:write |
readOnlyHint | false |
destructiveHint | false |
idempotentHint | true |
openWorldHint | true |
| REST call | PUT /v1/automations/{automation_id}/status |
#What it does
- Changes data in your account. It does not send messages to contacts.
- May start automations of the account, and an automation may send messages. The call itself sends nothing.
- Setting it active lets messages go to contacts later. The call itself sends nothing.
- Safe to repeat. With the same idempotency_key the first answer comes back.
#Input
The tool takes one flat object. Path, query and body fields of the REST call are merged into it.
| Name | Type | Required | Description |
|---|---|---|---|
automation_id | string | yes | Automation ID. |
status | string | yes | draft is saved and never runs (an automation that was active cannot go back to draft, use paused). active runs and needs the permission automations:run. paused stops without losing waiting messages. one of: draft, active, paused |
Arguments added by the MCP server (see Special arguments)
| Name | Type | Required | Description |
|---|---|---|---|
idempotency_key | string | no | Optional. Unique key, for example a UUID. Same key and arguments within 24 hours: first result. up to 255 characters |
#Result
The result has the same content as the REST answer. Lists have at most 50 items per page (default 20); use cursor for the next page.
Errors come back as a tool result with isError: true. The error codes are the ones in Errors.