Application example Bindings

Use Workflows in a real application path

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

A compact Workflows recipe with config and worker usage in one application path.

Use this as the copyable starter before threading the feature into a larger application.

Config focus: bindings.workflows
Runtime shape
Best use: starting long-running workflow instances from a Worker path

Start by wiring the binding clearly in config

Smallest Workflow binding config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'workflow-client',

bindings: {

workflows: {

ORDER_WORKFLOW: {

name: 'order-workflow',

className: 'OrderWorkflow'

}

})

Build the application flow around the binding

Treat this as the app-level Workflows path: the route, event handler, or service module receives a real request and uses the binding to do useful work.

Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.

Keep the first example short enough to paste into a new Worker.
Cloudflare owns deployed Workflow durability, retries, scheduling, and production instance history.

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 })

}

Keep production boundaries visible

Config focus: bindings.workflows.
Runtime shape: .
Best use: starting long-running workflow instances from a Worker path.

Thread this into the next recipe

Once this smallest path works, add routing, generated types, and feature-specific abstraction in that order.

Testing Workflows

Test Workflows by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.

Pipelines

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