post_v1_automations_connectors_id_run
Run executes one connector action in-process and answers the outcome. The caller's resolved credential travels in `auth`, delivered to the action verbatim — the runtime resolves no credential itself.
Run executes one connector action in-process and answers the outcome. The
caller's resolved credential travels in auth, delivered to the action
verbatim — the runtime resolves no credential itself. An action that ran and
failed (or an action name the connector does not have) answers ok:false with
the failure message, not an HTTP error; an unknown connector is 404 and a
missing action 422.
| Tool | post_v1_automations_connectors_id_run |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/automations/connectors/{id}/run |
| Product | automations |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
action | string | — | — | — | Action is the name of the connector action to invoke. |
auth | object | — | — | — | Auth is the caller's resolved credential for the connector, handed to the action verbatim. Its shape is whatever the connector's auth descriptor declares (a token string, an object), so it is opaque here. |
id | string | — | — | — | ID is the connector to run, from the path. |
props | object | — | — | — | Props are the action's input properties, keyed by property name. |
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_automations_connectors_id_run",
"arguments": {
"action": "<action>",
"auth": {},
"id": "<id>",
"props": {}
}
}
}'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_automations_connectors_id_run | POST /v1/automations/connectors/{id}/run | automations | Run executes one connector action in-process and answers the outcome. |
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).
How is this guide?