post_v1_automations_flows_id_versions

CreateVersion adds a new DRAFT version to a flow. The version is created invalid unless it carries a trigger, and it does not become the running version until it is published (PATCH the flow's publishedVersionId) or becomes the latest.


Tool	`post_v1_automations_flows_id_versions`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	3
Operation	`POST /v1/automations/flows/{id}/versions`
Product	automations

Arguments

Field	Type	Required	Default	Values	Description
`displayName`	`string`	—	—	—	DisplayName names the new version.
`id`	`string`	—	—	—	ID is the flow to add a version to, from the path.
`trigger`	`FlowTrigger`	—	—	—	Trigger is the root of the version's step tree. Optional: a version with no trigger is created invalid, and cannot run until one is set.

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`	—	—	—	—

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_automations_flows_id_versions",
         "arguments": {
           "displayName": "<displayName>",
           "id": "<id>",
           "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
`post_v1_automations_flows_id_versions`	`POST /v1/automations/flows/{id}/versions`	automations	Adds a new DRAFT version to a flow.

The same capability over plain HTTP is in the automations 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).