Hanzo
Cloud MCPmarketing

post_v1_marketing_sequences

Registers a drip sequence in the caller's org. Name is required; status defaults to draft, and a sequence must be ACTIVE before it will accept enrollments.

Registers a drip sequence in the caller's org. Name is required; status defaults to draft, and a sequence must be ACTIVE before it will accept enrollments. The id, createdAt and updatedAt of the input are ignored — the server assigns them.

Toolpost_v1_marketing_sequences
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments5
OperationPOST /v1/marketing/sequences
Productmarketing

Arguments

FieldTypeRequiredDefaultValuesDescription
createdAtintegerCreatedAt and UpdatedAt are unix seconds, both server-assigned.
idstringID is the server-assigned sequence id ("seq_" + 128 random bits).
namestringName is the sequence's label. Required, trimmed, capped at 1024 bytes.
statusstringStatus is the lifecycle: draft, active or archived. Empty means draft, and ONLY an active sequence accepts enrollments.
updatedAtinteger

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_marketing_sequences",
         "arguments": {
           "createdAt": 0,
           "id": "<id>",
           "name": "<name>",
           "status": "<status>",
           "updatedAt": 0
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. createdAt and updatedAt hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are 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

OperationRouteProductSummary
post_v1_marketing_sequencesPOST /v1/marketing/sequencesmarketingRegisters a drip sequence in the caller's org.

The same capability over plain HTTP is in the marketing 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?

On this page