Documentation menu

Developer API · resource

Workflows

Node-based automations (trigger → actions). Nodes and edges are exposed as read-only children.

Scope workflows:read for reads · workflows:write for changes

Operations

GET/v1/workflowsList — see list
POST/v1/workflowsCreate — see create
GET/v1/workflows/{id}Read — see get
PATCH/v1/workflows/{id}Update — see update
DELETE/v1/workflows/{id}Delete — see delete
Minimal create
curl -X POST https://api2.djcsystem.com/v1/workflows \
  -H "Authorization: Bearer $DJC_TOKEN" -H "Content-Type: application/json" \
  -d '{ "name": "…" }'

Fields

Fields you may send on create. Updatable marks fields accepted by PATCH. Anything not listed is server-owned or hidden.

FieldTypeOn createUpdatable
namestringrequiredyes
statusenum(active|inactive)optionalyes

Filters & sorting

Filterablestatus
Sortabledate
Default orderid order

Child: nodes

Workflow nodes (read-only).

GET/v1/workflows/{id}/nodes

Child: edges

Workflow edges (read-only).

GET/v1/workflows/{id}/edges

Child: executions

Recent runs (read-only).

GET/v1/workflows/{id}/executions

Good to know

  • The graph editor owns nodes/edges; this API exposes them read-only so agents can explain and audit automations.