Skip to main content
PATCH
Save workflow draft

Authorizations

Authorization
string
header
required

Organization API key, generated in studio.sidenet.ai. Backend only — never in a browser.

Path Parameters

id
string
required
Example:

"4c2f9e18-7a63-4d05-b1e8-93a7c0f2d641"

Body

application/json
definition
object

The steps + flow graph. Validate it against GET /v1/workflows/definition-schema. Its optional top-level output_text is the result-message template posted after a successful run — {{ $.input. }} / {{ $.steps.. }} placeholders resolve against the run. Omitted, the built-in result summary writes the message: a model reads the run and writes the answer, rendering rich-UI components; steer it with output_summary.instructions, or disable it with output_summary.enabled: false for a plain completion notice with the output attached.

Example:
input_schema
object
Example:
output_schema
object
Example:
name
string

The workflow's name. Workflow-level, not versioned — it takes effect immediately, with no publish.

Example:

"Classify support requests"

description
string

The workflow's description. Workflow-level, not versioned — same immediate effect as name. Send null to clear it.

Example:

"Routes each incoming request to a category."

Response

The saved draft

workflow
object

The workflow row, reflecting any name / description change in this save.

draft
object

The whole draft after the merge, not just the fields you sent. rev has been bumped by the DB. Saving does not publish: the active version keeps running until POST /v1/workflows/{id}/publish and /activate.