# Workflows, Workers - Declare Workflows in the \`exports\` configuration

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Cloudflare Developers
- Category: Cloud
- Original publication time: 2026-09-24T00:00:00Z
- First observed by NexusTechWire: 2026-10-01T15:54:33Z
- Original source: https://developers.cloudflare.com/changelog/post/2026-09-24-workflow-exports/
- NexusTechWire record: https://nexustechwire.com/news/news-6b85701dc6fb1872c487

## From the publisher

You can now declare the Workflows a Worker defines in the exports field of your Wrangler configuration file. Previously, a Worker could only define a Workflow through a workflows binding, even when the Worker never called the Workflow itself. Key each entry by the name of the class that extends WorkflowEntrypoint: \{ "exports": \{ "MyWorkflow": \{ "type": "workflow", "name": "my-workflow", "limits": \{ "steps": 25000, \}, "schedules": \["0 \* \* \* \*"\], \}, \}, \} \[exports.MyWorkflow\] type = "workflow" name = "my-workflow" schedules = \[ "0 \* \* \* \*" \] \[exports.MyWorkflow.limits\] steps = 25\_000 A workflow export accepts the same settings as a workflows binding: limits, schedules, and default\_retention. When you run wrangler deploy, Wrangler creates or updates the Workflow with these settings. You can declare a Workflow as both a binding and an export.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Cloudflare Developers](https://developers.cloudflare.com/changelog/post/2026-09-24-workflow-exports/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.