patch_v1_automations_flows_id
UpdateFlow updates one automation's metadata in place. Every field is optional; a field the request omits is left alone.
UpdateFlow updates one automation's metadata in place. Every field is optional; a field the request omits is left alone. Publishing a version pins which one runs, and is refused unless that version belongs to this flow.
| Tool | patch_v1_automations_flows_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | PATCH /v1/automations/flows/{id} |
| Product | automations |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
externalId | string | — | — | ExternalID sets the caller's own id for this flow. |
folderId | string | — | — | FolderID moves the flow in the builder's tree. |
id | string | — | — | ID is the flow to update, from the path. |
metadata | any | — | — | Metadata replaces the caller's opaque JSON. |
publishedVersionId | string | — | — | PublishedVersionID pins the version runs execute. It must name a version OF THIS FLOW; empty clears the pin, so runs take the latest version again. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "patch_v1_automations_flows_id",
"arguments": {
"externalId": "<externalId>",
"folderId": "<folderId>",
"id": "<id>",
"metadata": "<metadata>",
"publishedVersionId": "<publishedVersionId>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_patch_v1_automations_flows_id | PATCH /v1/automations/flows/{id} | automations | UpdateFlow updates one automation's metadata in place. |
The same capability over plain HTTP is in the automations API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?