post_v1_flow_runs
Run executes one of the caller's workflows synchronously: the graph runs in the flow service and the response carries the run's session and outputs.
Run executes one of the caller's workflows synchronously: the graph runs in the flow service and the response carries the run's session and outputs. A graph whose components fail reports the product's own error. Runs are bounded by the product's five-minute sync ceiling.
| Tool | post_v1_flow_runs |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/flow/runs |
| Product | flow |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
input | string | — | — | Input is the run's chat input value, handed to the graph's input node. |
session | string | — | — | Session groups runs into one conversation; the product mints one when absent and returns it in the response. |
tweaks | any | — | — | Tweaks override component fields for this run only (the product's tweaks document), verbatim. |
workflow | string | — | — | Workflow is the UUID of the workflow to run. |
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_flow_runs",
"arguments": {
"input": "<input>",
"session": "<session>",
"tweaks": "<tweaks>",
"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_post_v1_flow_runs | POST /v1/flow/runs | flow | Run executes one of the caller's workflows synchronously: the graph runs in the flow servi |
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?