patch_v1_flow_workflows_workflow
WorkflowUpdate patches one of the caller's workflows: name, description, graph, or the locked flag — only the stated fields move.
WorkflowUpdate patches one of the caller's workflows: name, description, graph, or the locked flag — only the stated fields move. Ownership is verified before the patch reaches the product.
| Tool | patch_v1_flow_workflows_workflow |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | PATCH /v1/flow/workflows/{workflow} |
| Product | flow |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
data | any | — | — | Data replaces the workflow graph when present, verbatim. |
description | string | — | — | Description replaces the description when present. |
locked | boolean | — | — | Locked freezes or unfreezes the workflow against edits when present. |
name | string | — | — | Name renames the workflow when present. |
workflow | string | — | — | Workflow is the workflow's UUID, taken from the path. |
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_flow_workflows_workflow",
"arguments": {
"data": "<data>",
"description": "<description>",
"locked": false,
"name": "<name>",
"workflow": "<workflow>"
}
}
}'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_flow_workflows_workflow | PATCH /v1/flow/workflows/{workflow} | flow | WorkflowUpdate patches one of the caller's workflows: name, description, graph, or the loc |
The same capability over plain HTTP is in the flow 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?