Skip to content

Pipelines

A pipeline is a state machine for records. It defines the stages a record can occupy and the transitions between them. A board can use those stages as columns.

A team pipeline names its storage list through definition.listRef. Declare unique stages with exactly one initial stage, and transitions whose fromStageId and toStageId both exist. A transition can map fields. A connector-backed transition in Studio references a pinned, registered single-operation playbook scoped to that team.

{
"key": "pipeline.meeting-desk.summaries",
"teamId": "meeting-desk",
"revision": 1,
"archived": false,
"kind": "pipeline",
"definition": {
"name": "Summary follow-up",
"description": "",
"listRef": "list.meeting-desk.summaries",
"stages": [
{
"id": "shared",
"name": "Shared",
"type": "initial"
},
{
"id": "done",
"name": "Done",
"type": "terminal"
}
],
"transitions": [
{
"id": "finish",
"name": "Mark done",
"fromStageId": "shared",
"toStageId": "done",
"fieldMappings": []
}
]
}
}

A new Meeting summaries record starts at Shared. Mark done moves it to Done when the team finishes the follow-up. Before moving a record, verify its current stage and apply the transition allowed from that stage. A transition that starts a protected connector operation must respect its grant and review. Use the result or receipt to decide when the record can advance.

Review existing records and app boards before removing or renaming a stage key. An app board references a pipeline for the same team and list. When the runtime rejects a stale transition, reload the record and evaluate the new stage before resubmitting.

See list definitions, apps, and the linked pipeline profile.