Workflow authoring
Discover schemas, edit graphs safely and configure triggers through REST
Check availability
Read Get authoring context. Graph patching and trigger configuration require authoringEnabled: true; unavailable authoring returns 503 AUTHORING_DISABLED. This documentation release does not enable authoring on your deployment.
Build from the node catalog
- Search node types to find a type and its operations.
- Get its schema for field definitions, outputs and connection handles.
- List connections using the provider ID returned by the schema. Connect new accounts through Innflow's UI.
- Create a workflow or import a complete graph.
- Get the workflow and retain
graphRevisionasexpectedRevision. - Patch the graph with a unique
Idempotency-Keyand up to 25 operations. - Configure triggers, then validate before deploying.
Graph operations
| Operation | Required fields beyond operation |
|---|---|
addNode | ref, type; optional name, position, data |
configureNode | nodeId, data |
removeNode | nodeId |
moveNode | nodeId, position |
connect | source, target; optional sourceHandle, targetHandle (default main) |
disconnect | source, target; optional sourceHandle, targetHandle (default main) |
Temporary ref values identify added nodes within a patch; the response's nodeIds maps them to saved IDs. Read the full graph request schema for constraints. Use handles returned by the node schema.
A revision conflict means another edit occurred. Refetch the graph, reconcile the intended change and submit with the new revision and a new operation key. Do not blindly overwrite another editor's work.
Provider setup and execution
A trigger response can report needs_input, provider_handoff or pending rather than configured. Inspect persisted, missing and instructions before treating setup as complete. Dynamic field selectors may return handoffUrl for editor-only setup.
Execution is asynchronous. Use the execution ID to read progress and the operation ID, when returned, to inspect its dispatch receipt.
MCP OAuth contract
MCP clients authenticate with OAuth and send X-Innflow-MCP-Contract: 1. On that authenticated contract, create, deploy, undeploy and execute use transactional operation receipts with a required idempotency key. Setting the header on a normal API-key request does not switch it into the MCP OAuth contract.
MCP deploy/undeploy accept an optional nonnegative expectedRevision. MCP execution and deferred deployment work can return 202, with operationId and idempotencyKey alongside data. Poll Get operation receipt. These semantics differ from the normal API-key endpoints; see the MCP reference for client setup.