Core concepts
Workflow
Section titled “Workflow”A workflow is an organisation-scoped TypeScript program with one seated-member
owner. The program uses defineWorkflow() and has one current revision.
Revision history
Section titled “Revision history”A revision is an immutable, valid, compiled version of the program. Creating or forking a workflow creates Version 1. Each changed Save appends and activates the next version. Invalid or canonically unchanged source creates no revision.
Undo and Restore append compensating revisions. They do not delete history or move the current pointer backward. Only the seated owner can save or restore. Other members, including organisation admins, inspect and fork.
Capability envelope
Section titled “Capability envelope”Every revision declares the effect kinds, networks, controlled accounts, transaction targets, HTTP host patterns, notification channels, and audiences it may use. This is authority, not documentation: a run cannot register an effect outside its frozen envelope.
Durable effect
Section titled “Durable effect”An effect is a stable-keyed request that leaves ordinary TypeScript execution. The initial catalog covers EVM and HTTP snapshots, event and timer waits, human confirmation/choice/forms, notifications, and EVM transaction lists. Cloudflare Workflows durably suspends and resumes the program; txcast remains authoritative for authorization, effect state, signing, notifications, and product history.
A run is created and started atomically from the current revision. Creation freezes the exact revision, artifact, backend, input, resolved references, capabilities, and limits. Its graph projects concrete effect occurrences and their causal relationships. The graph is not a separate execution definition.
Observation and refresh
Section titled “Observation and refresh”An EVM or HTTP snapshot produces an immutable observation. The value first consumed by the program never changes. A manual refresh appends another observation and may update the dashboard’s selected view, but it does not rewrite program history or reactivate downstream work.
Human and wallet boundary
Section titled “Human and wallet boundary”Human effects can be resolved only by eligible members; organisation admins may perform an audited override. Transactions always require eligible wallet interaction. Agents may author, save, stage, start, inspect, cancel, and request a source refresh when scoped. Agents cannot answer human effects or sign.