Updates an existing workflow definition. The workflow must already exist and belong to the workspace associated with your API key.
This endpoint updates the workflow metadata and creates a new version with the provided nodes, edges, and configuration. It does not create new workflows — if the provided id does not match an existing workflow in your workspace, the request will fail.
Versioning: Every call to this endpoint creates a new workflow version. Versions are immutable and auto-increment. The previous version is preserved and can be referenced by version number.
Typical usage:
GET /workflows/{workflow_id} to fetch the current workflow definitionnodes, edges, or other fields as neededPOST /workflows with the full updated payload to save a new versionImportant: This endpoint requires the full workflow definition. Partial updates are not supported — you must include all required fields (nodes, edges, schemas) even if they haven’t changed.
API key-based authentication. Provide your CloudCruise API key in the cc-key header.
Payload for updating an existing workflow. The recommended approach is to first fetch the
current workflow via GET /workflows/{workflow_id}, modify the desired fields, and then
submit the full payload here.
The workflow must already exist in the workspace associated with your API key.
Unique identifier for the workflow to update. Use the id from the
GET /workflows/{workflow_id} response. The workflow must already exist in your workspace.
Display name of the workflow
Array of workflow step nodes. Each node represents an action in the workflow (e.g., click,
type text, navigate, extract data). Pass an empty array [] to clear all nodes.
Map of edges connecting workflow nodes. Keys are source node IDs, values define the outgoing
connections. Pass an empty object {} to clear all edges.
JSON Schema defining the workflow's input variables
{
"type": "object",
"properties": {
"SEARCH_TERM": { "type": ["string", "null"] }
},
"required": ["SEARCH_TERM"]
}JSON Schema defining the workflow's output variables
{ "type": "object", "properties": {} }Maximum number of retry attempts for failed workflow steps
0
Optional description of the workflow
Optional note describing what changed in this version
"Updated login selectors"
Whether to use native browser actions instead of simulated events
Whether to record a video of the workflow execution
URL patterns to extract from network traffic during execution
References to encrypted vault keys used by this workflow
XPath selectors for popups that should be automatically dismissed
Schema defining vault credentials required by this workflow
{
"USER": {
"type": "credential",
"domain": "https://example.com",
"example": "11223344-5566-7788-9900-112233445566"
}
}Proxy configuration setting
Proxy value (e.g., proxy URL or region)
Whether popup handling is enabled
Whether action timing recovery is enabled
Whether XPath recovery is enabled
Whether error code generation is enabled
Whether service unavailable recovery is enabled
Whether the network listener is enabled
Workflow upserted successfully. Returns the full workflow with the new version number.
Full workflow definition including nodes and edges
Unique identifier for the workflow
Name of the workflow
Timestamp when the workflow was created
Timestamp when the workflow was last updated
ID of the workspace this workflow belongs to
ID of the user who created the workflow
Array of workflow step nodes
Map of edges connecting workflow nodes
Description of the workflow
Current version number of the workflow
ID of the current workflow version
JSON schema defining the workflow's input variables
Schema defining vault credentials and their configuration
Whether popup handling is enabled for this workflow
Whether XPath recovery is enabled for this workflow
Whether error code generation is enabled for this workflow
Whether service unavailable recovery is enabled for this workflow
Whether action timing recovery is enabled for this workflow
ID of the catalog workflow this was forked from (if applicable)
Version number of the catalog workflow this was forked from
Whether to track updates from the origin catalog workflow