Automations
Update or publish an automation
One endpoint, two mutually-exclusive modes:
- Update — supply one or more of
name,description,nodes,connections,triggerEventId. Graph updates persist a newautomationVersionIdon the sameautomationId. AdddryRun: trueto validate a graph update without persisting. - Lifecycle — supply
published: trueto promote the stored latest version live (validates the graph first →409 PUBLISH_VALIDATION_FAILEDon blockers; optionally pinautomationVersionIdto publish a specific version), orpublished: falseto unpublish.
The two modes cannot be combined: publishing promotes the stored graph, so update first, then PATCH { "published": true }. Returns the bare automation row.
PATCH
Authorizations
Send your Brew API key as Authorization: Bearer brew_xxx.
Path Parameters
Automation id returned by POST /v1/automations and listed by GET /v1/automations.
Required string length:
1 - 64Example:
"auto_abc"
Body
application/json
Required string length:
1 - 120Maximum string length:
2000Maximum array length:
500- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Maximum array length:
1000Required string length:
1 - 256Required string length:
1 - 64Response
Updated / published / unpublished. The bare automation row (or the dry-run result when dryRun: true).
Required string length:
1 - 64Required string length:
1 - 64Required string length:
1 - 120Required range:
x >= 0Required string length:
1 - 64Required string length:
1 - 256Maximum string length:
2000- Option 1
- Option 2
- Option 3
- Option 4
- Option 5