post_v1_flow_workflows
WorkflowCreate creates a workflow in the caller's org.
WorkflowCreate creates a workflow in the caller's org. The org's project id is pinned server-side from the validated principal — there is no field by which a caller could place a workflow in another org.
| Tool | post_v1_flow_workflows |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/flow/workflows |
| Product | flow |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
data | any | — | — | — | Data is the workflow graph (the product's nodes/edges document), verbatim. Omit it to create an empty workflow. |
description | string | — | — | — | Description says what the workflow does. |
name | string | — | — | — | Name is the workflow's display name, unique within the org's project (the product de-duplicates by suffixing). |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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_flow_workflows",
"arguments": {
"data": "<data>",
"description": "<description>",
"name": "<name>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. 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 |
|---|---|---|---|
post_v1_flow_workflows | POST /v1/flow/workflows | flow | Creates a workflow in the caller's org. |
The same capability over plain HTTP is in the flow API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?