API ReferenceWorkflows
Save, publish or archive a canvas workflow (human member or management API key).
Save, publish or archive a canvas workflow (human member or management API key). - Rensei REST API operation reference.
PUT
header
AuthorizationBearer <rsk_live_*>Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
id*stringWorkflow id.
application/json- body
name?stringdescription?string|nullstatus?stringValue in
"configuring""draft""published""archived"confirmUnpublish?booleanRequired to flip a published workflow back to draft.
nodes?array<unknown>edges?array<unknown>groups?array<unknown>providerRequirements?array<>|nullworkflowConfig?|nulldefinitionVersion?stringExplicit executable workflow grammar. Omission preserves auto-detection for legacy callers.
Value in
"2""1.1"lifecycle?|Embedded lifecycle carrier. Omission retains the stored value; null clears it.
lifecycleRef?|Project lifecycle reference. Omission retains the stored value; null clears it.
definitionMetadata?viewport?unknownsourceComments?Workflow updated.
application/json- response
id*stringworkspaceId*stringname*stringdescription*string|nullstatus*stringnodes*array<unknown>edges*array<unknown>groups*array<unknown>providerRequirements*unknown|nullworkflowConfig*unknown|nulltriggerConfig*unknown|nullviewport*unknowndefinitionYaml*string|nullcreatedBy*stringcreatedAt*stringupdatedAt*stringpublishedAt*string|nullarchivedAt*string|nullcurl -X PUT 'https://app.rensei.ai/api/workflows/string' \ -H 'Content-Type: application/json' \ -d '{}'Example Response
{ "id": "string", "workspaceId": "string", "name": "string", "description": "string", "status": "string", "nodes": [ null ], "edges": [ null ], "groups": [ null ], "providerRequirements": null, "workflowConfig": null, "triggerConfig": null, "viewport": null, "definitionYaml": "string", "createdBy": "string", "createdAt": "string", "updatedAt": "string", "publishedAt": "string", "archivedAt": "string"}