Cloudflare Workflows
developers.cloudflare.com
- Free plan
- Web
- API
What Cloudflare Workflows is
Cloudflare Workflows lets developers build multi-step applications on Cloudflare Workers without managing infrastructure. It supports durable steps, automatic retries, error handling, and state that can persist for minutes, hours, or weeks. A workflow can pause for seconds, hours, or days, or wait for a webhook, user input, or an external system response before proceeding. Instances can be triggered, paused, resumed, and terminated programmatically or through an API. Workflows can make Fetch API requests and call Cloudflare services including R2, KV, and D1; developers can invoke them through the Workers API, Wrangler CLI, or REST API. Billing covers CPU time, requests, persisted storage, and executed steps, while waiting or sleeping does not incur CPU time. The free plan is included with Workers Free, with usage limits. Paid pricing starts at $5/mo, and paid plans allow up to five minutes of CPU time per invocation. Workflows cannot be deployed to Workers for Platforms namespaces.
Who it suits
Cloudflare Workflows suits developers building applications with multi-step tasks that may need retries, persisted state, or pauses while waiting for an event or response. It is for applications built on Cloudflare Workers.
Good to know, and what to watch
- Retries failed tasks and handles errors.
- State can persist for minutes, hours, or weeks.
- Can pause or wait for external events.
- Instances can be managed through code or an API.
- Waiting and sleeping do not incur CPU time.
- Cannot deploy to Workers for Platforms namespaces.
- Free usage is subject to limits.
- Paid plans allow up to five minutes of CPU time per invocation.
Plans
Every plan and priceWorkers Paid
Workers Free
Free plan · paid from $5/mo
The verdict
Workflows provides durable execution and event waits for applications on Cloudflare Workers. Check the deployment restriction and usage limits against your requirements.
What the maker publishes
- API access
- Workflows can be invoked through the Workers API, Wrangler CLI, or REST API. source
- Deployment restriction
- Workflows cannot be deployed to Workers for Platforms namespaces because Workflows do not support Workers for Platforms. source
- Durable execution
- Workflows supports durable steps with automatic retries and error handling. source
- External events
- A Workflow can wait for webhooks, user input, or external system responses before continuing. source
- Founded
- 2009 source
- Headquarters
- San Francisco, California, USA source
- Instance management
- Workflow instances can be triggered, paused, resumed, and terminated programmatically or through an API. source
- Integrations
- The documentation identifies Fetch API requests and Cloudflare services including R2, KV, and D1 as services a Workflow can call. source
- Limits
- A Workflow step has unlimited wall-clock duration, but its CPU time is subject to the configured limit; paid plans allow up to five minutes of CPU time per invocation. source
- Purpose
- Cloudflare Workflows lets developers build durable multi-step applications on Cloudflare Workers without managing infrastructure. source
- Retries and state
- Workflows can automatically retry failed tasks and persist state for minutes, hours, or weeks. source
- Scheduling
- Workflows can pause for seconds, hours, or days using step.sleep() and step.sleepUntil(). source
- Support
- The Workflows documentation directs users to the Workers community on Discord to ask questions and discuss the platform. source
- Usage billing
- Workflows are billed for CPU time, requests, persisted storage, and executed steps, while waiting or sleeping does not incur CPU time. source
Checked against the maker's pages on 29 Sept 2026.