Skip to main content
POST
Create workflow

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json

A new workflow. Created as a draft; use the activate operation to make it run.

project_id
string
required

Project the workflow belongs to. You must have editor access to it.

Minimum string length: 1
title
string
required

Workflow name, shown wherever it is listed.

Required string length: 1 - 255
description
string
default:""

Optional longer description.

Maximum string length: 2000
status
enum<string>
default:draft

Workflow state. A workflow becomes active only through the activate operation, which freezes the version that runs.

Available options:
draft,
paused,
archived
output_folder
string
default:""

Project folder the workflow writes its outputs to, for example /Reports.

Maximum string length: 512
graph
Graph · object | null

The workflow's graph document: the nodes it runs and how they connect, as {"nodes": [...], "edges": [...]}. This is the FULL desired document on every create and update, not a patch — what you send replaces the stored graph. It must contain a trigger node, summation.trigger.schedule/v1 or summation.trigger.manual/v1, wired to the first work node by an edge {"from_node": "", "from_port": "inputs", "to_node": "", "to_port": "inputs"}. Each node is {"key", "type", "config"}; the node type ids you may use and the config each one takes come from GET /v1/workflows/node-types. A config carries ONLY the keys its node type declares there — any other key is refused, so a field the node type does not name cannot be smuggled through it. Use the summation.trigger.schedule/v1 node exactly when this request also carries schedule triggers; see the triggers field. Omit to create an empty draft. Serializes to at most 200000 characters. The web editor adopts API-authored graphs and normalizes them to its canonical form on its next save.

triggers
WorkflowTriggerRequest · object[]

Schedules that start this workflow. Omit for a workflow that only runs on demand. These rows and the graph's trigger nodes must agree: a schedule here requires a summation.trigger.schedule/v1 node in the graph — it is the node the schedule's parameter values are bound to — and that node requires a schedule here, or nothing would fire it. A request where the two disagree is refused.

Maximum array length: 20

Response

Successful Response

data
Workflow · object
required