For the complete documentation index, see llms.txt. This page is also available as Markdown.
Update Workflow
Update an existing workflow by entity ID. The request body must be the full workflow graph — the server replaces the entire stored graph, so partial field updates are not supported.
The checksum from the last Get workflow by id, Create, or Update response is required. If it does not match the server's current checksum, the update is rejected.
On success, the response returns a new data.checksum — store it before calling test or publish.
Update workflow
patch
Update an existing workflow by entity ID.
Send the full workflow graph — the server replaces the entire stored graph. Partial field updates are not supported.
Recommended flow:
GET /dev/v1/workflow/{entity-id} → copy data and data.checksum
Modify the fields you need
PATCH with the full modified document + checksum from step 1
checksum is required. If it does not match the server's current checksum the update is rejected.
On success: response returns a new data.checksum — store it before calling test or publish.
Your Nected API key. Obtain from your workspace settings.
Path parameters
entity-idstringRequired
The workflow entity ID
Example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
Header parameters
Nected-BranchstringOptional
Branch name (optional)
Body
Request body for Update workflow. Send the full workflow graph (same shape as Create) plus checksum.
Do not send partial field updates — the server replaces the full graph. Recommended: get the current document, modify it, send it back with the current checksum.
Canonical file: Update/update_workflow.json.
checksumstringOptional
Current checksum from the last get/create/update — required for optimistic locking
namestringOptional
descriptionstringOptional
startNodestringOptional
triggerobjectOptional
commentstringOptional
isEnabledbooleanOptional
Other propertiesanyOptional
Responses
200
OK — returns new data.checksum.
application/json
Success response for PATCH /dev/v1/workflow/{entity-id}