mcpProvider-backed
Run workflow
tools/call
Execute an explicitly identified saved workflow against a batch of input records. Never use this for a generic content request. Each record is one row processed by the DAG end-to-end. Execution is fire-and-forget - the route returns 202 with an execution_id immediately; poll list-workflow-runs or get-workflow-run for status.
Parameters
workspaceId
string
Optional workspace ID or slug. Required when this credential can access multiple workspaces and no workspace was configured on the client.
workflowIdrequired
string
Workflow UUID to execute.
recordsrequired
object[]
Array of input records, one per row to process. Shape matches the workflow's expected input schema.
Example
MCP tools/calljson
{"jsonrpc": "2.0","id": 1,"method": "tools/call","params": {"name": "run-workflow","arguments": {"workflowId": "00000000-0000-4000-8000-000000000000","records": [{}]}}}
Response
The operation is available, but its typed response schema has not been published yet.
JSON-RPC errors
- -32602
- Invalid parameters. Field-level details are returned in the JSON-RPC error data.
- -32001
- Authentication or hosted AI consent is required.
- -32003
- Workspace access is denied.
- -32029
- The request was rate limited.