Automations
Update automation
Rename an automation, turn it on or off, or repair it with a corrected definition
PUT
Update automation
This endpoint has two modes:
A request with none of
- Rename / toggle — pass
nameand/orenabledto rename the automation or turn it on/off. - Repair — pass a corrected
flowdefinition and the automation is rebuilt in place, re-tested with a real run, and re-activated only when the test passes. Use this after diagnosing a failure with Get automation and List automation runs.
Path Parameters
The ID of the automation (from List automations)
Request body
A new name for the automation (max 255 characters). In repair mode, the current name is kept when omitted.
Repair mode: the corrected full definition, in the same format as Create automation (
{"trigger": {...}, "steps": [...]}). Max 1 MB.Sample payload for the repair test run (for assistant events, the canonical sample is used when omitted). Max 256 KB.
For repairs of assistant-event automations: the assistant to (re)attach to. Usually already carried inside the definition’s trigger.
Required (
true) when the corrected definition contains steps that send messages or emails, start calls, or make non-GET HTTP requestsname, enabled or flow returns a 422 asking for at least one of them.
Response — rename / toggle
Response — repair
The same envelope as Create automation (automation_id, status, test, response, binding), without webhook_url — a repaired automation keeps its original webhook URL. Returned with HTTP 200; status is active, active_untested or test_failed. A repair whose test fails leaves the automation disabled; a repair rejected before the test run (e.g. no_steps) leaves the existing automation untouched.
A missing automation — or one that does not belong to your account — returns a 404 with {"message": "Automation not found"}.

