cloudflare-workflows

Manage durable multi-step workflows on Cloudflare Workers with state persistence.

22|1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/itechmeat/llm-code --skill cloudflare-workflows-itechmeat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudflare-workflows
Source: https://github.com/itechmeat/llm-code/tree/main/skills/cloudflare-workflows
Command: npx skills add https://github.com/itechmeat/llm-code --skill cloudflare-workflows-itechmeat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a guided approach to building durable, multi-step workflows on Cloudflare Workers, enabling state persistence, retries, sleep scheduling, and event-driven orchestration.

Core Features & Use Cases

  • Durable orchestration with WorkflowEntrypoint and WorkflowStep
  • Sleep and scheduling, wait for external events, and send events
  • Batch lifecycle management, error handling, and workflow bindings
  • Real-world use cases include long-running processes, approvals, and saga-style compensations

Quick Start

Create a workflow worker that uses step.do to perform tasks, step.sleep to pause, and step.waitForEvent to react to external events, then expose controls via Wrangler.

Frequently Asked Questions about cloudflare-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build durable workflows on Cloudflare Workers that survive restarts?

Durable workflows on Cloudflare Workers persist state across steps and restarts by implementing WorkflowEntrypoint and WorkflowStep, allowing long-running processes to resume execution exactly where they left off.

What is the best way to handle retry backoff and sleep scheduling in serverless workflows?

Retry backoff and sleep scheduling in serverless workflows are handled using step.do for task execution and step.sleep for pausing, ensuring state persistence across retry attempts and scheduled delays.

How do I coordinate external events for long-running approvals in Cloudflare Workers?

External events for long-running approvals are coordinated using step.waitForEvent to pause execution until triggered and sendEvent to deliver external signals, enabling saga-style compensations across distributed services.

Can I manage batch lifecycle and workflow bindings for event-driven processes on Cloudflare?

Batch lifecycle and workflow bindings for event-driven processes on Cloudflare are managed through lifecycle bindings that expose controls via Wrangler, enabling deployment and monitoring of multi-step workflow instances.

When do I need durable workflow orchestration instead of standard serverless functions?

Durable workflow orchestration is needed for long-running, event-driven processes requiring state persistence, retries with backoff, and external event coordination, which standard stateless serverless functions cannot maintain.

Does this approach support saga-style compensations across distributed services?

Saga-style compensations across distributed services are supported by orchestrating multi-step workflows with error handling and event coordination, ensuring state consistency through WorkflowStep retries and sleep scheduling.