post_v1_automations_flows

CreateFlow creates an automation and its initial DRAFT version in one call. The new flow is DISABLED — creating it does not arm its trigger; POST /v1/automations/flows/{id}/enable does that.


Tool	`post_v1_automations_flows`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	4
Operation	`POST /v1/automations/flows`
Product	automations

Arguments

Field	Type	Required	Default	Values	Description
`displayName`	`string`	—	—	—	DisplayName names the flow's initial draft version.
`externalId`	`string`	—	—	—	ExternalID is the caller's own id for this flow. Optional.
`folderId`	`string`	—	—	—	FolderID groups the flow in the builder's tree. Optional.
`trigger`	`FlowTrigger`	—	—	—	Trigger is the root of the step tree — how the flow starts, and the action chain that follows. Optional: a flow may be created empty and edited later.

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.

Object types

FlowAction, FlowTrigger and StepSettings are objects this tool's fields are made of. Each is declared inside the tool's own schema, and each is enumerated in full below.

FlowAction

Field	Type	Required	Default	Values	Description
`displayName`	`string`	—	—	—	—
`name`	`string`	—	—	—	—
`nextAction`	`FlowAction`	—	—	—	—
`settings`	`StepSettings`	—	—	—	—
`skip`	`boolean`	—	—	—	—
`type`	`string`	—	—	—	PIECE \| CODE \| ROUTER \| LOOP_ON_ITEMS
`valid`	`boolean`	—	—	—	—

FlowTrigger

Field	Type	Required	Default	Values	Description
`displayName`	`string`	—	—	—	—
`name`	`string`	—	—	—	—
`nextAction`	`FlowAction`	—	—	—	—
`settings`	`StepSettings`	—	—	—	—
`strategy`	`string`	—	—	—	—
`type`	`string`	—	—	—	PIECE_TRIGGER \| EMPTY
`valid`	`boolean`	—	—	—	—

StepSettings

Field	Type	Required	Default	Values	Description
`actionName`	`string`	—	—	—	—
`input`	`object`	—	—	—	—
`pieceName`	`string`	—	—	—	—
`pieceVersion`	`string`	—	—	—	—
`triggerName`	`string`	—	—	—	—

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_automations_flows",
         "arguments": {
           "displayName": "<displayName>",
           "externalId": "<externalId>",
           "folderId": "<folderId>",
           "trigger": {
             "displayName": "<displayName>",
             "name": "<name>",
             "nextAction": {},
             "settings": {},
             "strategy": "<strategy>",
             "type": "<type>",
             "valid": false
           }
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. trigger.valid holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation 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
`cloud_post_v1_automations_flows`	`POST /v1/automations/flows`	automations	CreateFlow creates an automation and its initial DRAFT version in one call.

The same capability over plain HTTP is in the automations API reference, on https://api.hanzo.ai.

All 833 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).