upstash / workflow-js

The skill documents @upstash/workflow: you declare a workflow endpoint with serve(), then break the work into named steps through the context object — context.run to execute a function, context.sleep or context.sleepUntil to pause, context.call to reach a third party without burning your own runtime, and context.waitForEvent / context.notify to coordinate across separate workflow runs. Each step gets Upstash's delivery guarantees and automatic retries on failure, backed by QStash underneath. A separate Client handles the outside view of a running workflow — trigger, cancel, notify, and getWaiters — for code that needs to start or manage a workflow rather than run inside one.

This is for someone already deploying to Next.js, Cloudflare Workers, or another serverless target who wants durable multi-step execution without standing up their own queue or state store — not someone comparing workflow engines in the abstract, since the skill only covers this one SDK. The package's own README frames it as GA and fully covered by Upstash's professional support, so it reads as a maintained product surface rather than an experiment.