Workflows, Workers - Call Workflows declared in exports through ctx.exports
Cloudflare Workers can now invoke Workflows declared in their exports configuration directly using ctx.exports , removing the requirement for a separate workflows binding.
Why this signal matters
Cloudflare has introduced direct access to Workflows defined within the same Worker via the execution context. Previously, triggering a Workflow required configuring an explicit workflows binding in the Worker's Wrangler configuration. With this update, any Workflow declared in the exports field can be accessed directly on ctx.exports keyed by its class name (e.g., ctx.exports.MyWorkflow.create({...}) ). The invocation interface mirrors the standard Workflow binding API.
Actionable summary
Cloudflare updated Workers and Workflows: Workers can now directly trigger self-declared Workflows via ctx.exports. instead of requiring a workflows binding. The exported instance maintains the standard Workflow binding API (such as .create() ).
- Agent usefulness
- 80/100
- Confidence
- 90%
- Canonical data
- JSON + Markdown
What builders should check
- Optionally refactor existing Worker code to call local Workflows via ctx.exports. instead of configuring separate workflows bindings in Wrangler.