# Workflows, Workers - Call Workflows declared in exports through ctx.exports

Category: agent-infrastructure
Published: 2026-09-27T00:00:00.000Z
Source: [Cloudflare Workflows changelog](https://developers.cloudflare.com/changelog/post/2026-09-27-workflow-ctx-exports/)
Agent usefulness: 80/100
Confidence: 0.9
Content mode: source-watch
Verified: 2026-09-28T12:17:31.535Z
Tags: cloudflare, workflows, changelog

## Human Summary
Cloudflare Workers can now invoke Workflows declared in their exports configuration directly using ctx.exports , removing the requirement for a separate workflows binding.

## Agent 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() ).

## Body
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.

## Recommended actions
- Optionally refactor existing Worker code to call local Workflows via ctx.exports. instead of configuring separate workflows bindings in Wrangler.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.