Binding reference Bindings

Use Workflows in a Worker

Workflows bindings let Workers start and inspect durable multi-step workflow instances.

Add the Workflows config, call from worker code, and start with the local test path Devflare supports.

Start with the config, wire the binding into worker code, then use the support section to decide whether local tests or Cloudflare-backed tests fit.

Config key
Authoring shape
Best for: starting long-running workflow instances from a Worker path

Add the binding to config

Add to , then use the generated env binding from Worker code.

Keep the first version close to the route or handler that needs it; move to a helper only after the shape is obvious.

Smallest Workflow binding config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'workflow-client',

bindings: {

workflows: {

ORDER_WORKFLOW: {

name: 'order-workflow',

className: 'OrderWorkflow'

}

})

Use the binding from application code

After Devflare generates the worker env, import from and keep the first Workflows path close to the route, handler, or service method that needs it.

Keep this first path small enough that the config, env binding, and user-visible behavior are easy to review together.

Define and start one order workflow

import { WorkflowEntrypoint, type WorkflowEvent, type WorkflowStep } from 'cloudflare:workers'

import { env } from 'devflare/runtime'

type OrderWorkflowParams = {

orderId: string

email: string

}

export class OrderWorkflow extends WorkflowEntrypoint<DevflareEnv, OrderWorkflowParams> {

async run(event: WorkflowEvent<OrderWorkflowParams>, step: WorkflowStep): Promise<unknown> {

const invoice = await step.do('create invoice', async () => {

return { id: 'inv_' + event.payload.orderId, email: event.payload.email }

})

await step.do('send confirmation', async () => {

await fetch('https://api.example.com/confirmations', {

method: 'POST',

body: JSON.stringify(invoice)

})

return { queued: true }

})

return invoice

}

export async function fetch(request: Request): Promise<Response> {

const orderId = new URL(request.url).searchParams.get('order') ?? 'demo'

const instance = await env.ORDER_WORKFLOW.create({

id: orderId,

params: { orderId, email: 'customer@example.com' }

})

return Response.json({ id: instance.id })

}

Local and Remote Support

Devflare can run useful Workflows application behavior locally for ordinary development and tests. Cloudflare still owns production limits, quotas, billing, and deployed account behavior.

Full local support through Miniflare workflow bindings and deterministic workflow mocks. Start locally with or ; that lane should cover the normal Workflows application flow without requiring a Cloudflare connection.

Use Cloudflare when the assertion depends on deployed limits, account state, lifecycle behavior, billing, or other production-only Workflows details.

When this binding fits best

Use Workflows when starting long-running workflow instances from a worker path.
Keep binding names stable and uppercase in examples so generated Env declarations remain predictable.
Prefer Devflare native config while it covers the feature; use only for unsupported Wrangler-only fields.

Testing path

Start with or for config-backed local worker tests.
Use / for small unit tests that only need deterministic application behavior.
Use Cloudflare-backed tests when the assertion depends on hosted platform behavior, account state, limits, billing, or production routing.

Open the next page when you need it

Subpage

Workflows internals

Internals

Check emitted Wrangler , preview behavior, and Cloudflare-specific details.

Subpage

Testing Workflows

Testing

Pick the or path first, then move to remote checks only when the test needs them.

Subpage

Workflows example

Example

Copy a fuller application path when the quick example is too small.