For the complete documentation index, see llms.txt. This page is also available as Markdown.
Create Workflow
Create a new workflow in your workspace. The request body must be the full workflow graph — name, nodes, edges, startNode, trigger, and settings. A minimal { "name": "..." } stub is not sufficient.
The response returns data.id (use for all subsequent operations) and data.checksum (required for update, test, and publish).
Create workflow
post
Create a new workflow. The request body must be the full workflow graph — not a minimal stub.
Required fields:name, nodes (must include the trigger node id: "1"), edges, startNode, trigger.
Every workflow must have a trigger node with id: "1", type: "trigger", data.nodeType: "apiTrigger". Its data.input map defines the API input schema — each key is a field name with dataType, executedValue (test sample), and metadata.
startNode must point to the first non-trigger executable node (skip addNode / addNodeMd UI placeholders).
trigger is always { "apiNode": "1" }.
Checksum: On success, data.id is the workflow entity ID (use for all subsequent calls) and data.checksum must be stored — required for update, test, and publish.
Create body ≈ GET data minus server fields (id, checksum, version, status, staticUrl, versionInfo, timestamps).
Your Nected API key. Obtain from your workspace settings.
Header parameters
Nected-BranchstringOptional
Branch name (optional)
Body
Request body for Create workflow.
Required fields:name, nodes (must include the trigger node with id: "1"), edges, startNode, trigger.
The full shape must match what you see in Get workflow by iddata (minus server-only fields like id, checksum, version, status, staticUrl, versionInfo, and timestamps).