post_v1_auto_flows
FlowCreate creates a flow in the caller's org.
FlowCreate creates a flow in the caller's org. The org is stamped server-side from the validated principal — there is no field by which a caller could place a flow in another org.
| Tool | post_v1_auto_flows |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | POST /v1/auto/flows |
| Product | auto |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
data | any | — | — | Data is the flow graph — the product's nodes/edges document, verbatim: nodes carry a piece type (webhook, schedule, http, set, branch) and its config; edges wire them. Omit it to create an empty flow. |
name | string | — | — | Name is the flow's display name. |
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": "post_v1_auto_flows",
"arguments": {
"data": "<data>",
"name": "<name>"
}
}
}'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_post_v1_auto_flows | POST /v1/auto/flows | auto | FlowCreate creates a flow in the caller's org. |
The same capability over plain HTTP is in the auto 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?