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.
Graph updates use the same strict typed filter/split condition contract as create: explicit type, canonical snake_case operator, no value for unary operators, and type-correct values everywhere else.
The two modes cannot be combined: publishing promotes the stored graph, so update first, then PATCH { "published": true }. Returns the bare automation row.
Authorizations
Send your Brew API key as Authorization: Bearer brew_xxx.
Headers
The brand this request acts on. REQUIRED for organization-scoped credentials (otherwise 400 BRAND_ID_REQUIRED — there is no default brand); list ids with GET /v1/brands. Brand-scoped credentials may omit it, and sending a different brand returns 403 BRAND_SCOPE_MISMATCH. A brand outside your organization returns 404 BRAND_NOT_FOUND.
1 - 64Path Parameters
Automation id returned by POST /v1/automations and listed by GET /v1/automations.
1 - 64"auto_abc"
Body
1 - 1202000500- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
10001 - 2561 - 64Response
Updated / published / unpublished. The bare automation row (or the dry-run result when dryRun: true).
1 - 641 - 641 - 120x >= 01 - 641 - 2562000- Option 1
- Option 2
- Option 3
- Option 4
- Option 5