Documentation
Workflows
A draft you author, a published version that is frozen, and the triggers that start it.
Draft and published
A workflow has one draft, which the builder edits, and a published version, which runs. Publishing validates the graph, the approval policy, the triggers and any sensitive knowledge it reaches, then freezes the definition and gives it a version.
A published definition is immutable. A run pins the version it started on, so a workflow that changes tomorrow does not change what happened yesterday.
What stays live inside a published workflow
Two things are deliberately not frozen, because freezing them would be wrong.
| Live | Consequence |
|---|---|
| The agents it names | Correcting an agent's instruction reaches steps that have not run yet, without republishing. |
| The connections its slots point at | Revoking a connection stops already-published workflows immediately. |
Triggers
| Trigger | Starts when |
|---|---|
| Manual | Somebody runs it. |
| Webhook | A request arrives at the workflow's own address. |
| Schedule | An interval or a cron expression, in a named timezone. |
| Polling | A watched source has something new. |
| API | Your systems start a run. See the API page. |
| Sub-workflow | Another workflow calls it as a step. |
Status
- Active runs normally.
- Paused keeps existing runs but stops triggers from starting new ones.
- Archived refuses new runs entirely.
- Deleted workflows go to trash and can be restored.