Upstash Workflow JS
UpstashOfficialCreated by Upstash
- Skill
- Tool integration
- Cloud and DevOps
- MIT
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Upstash Workflow SDK enables developers to create reliable, multi-step workflows within serverless environments. By leveraging QStash, it allows functions to survive timeouts, retries, and restarts, effectively managing long-running processes that span minutes or days without keeping the underlying function execution active. It supports complex orchestration patterns, including step-by-step execution, external API calls, event waiting, human-in-the-loop approvals, and sophisticated flow control.
What it does
- Exposes serverless endpoints for durable workflow execution.
- Manages multi-step processes that persist across function restarts and timeouts.
- Provides tools for flow control, including concurrency, rate limiting, and parallelism.
- Supports advanced patterns like cross-workflow invocation and waiting for external events.
- Enables local development and testing via the QStash dev server.
- Facilitates human-in-the-loop workflows and real-time updates.
When to use it
- When building long-running tasks that exceed standard serverless function execution limits.
- When implementing saga or orchestration patterns in a distributed system.
- When you need reliable background jobs with built-in checkpointing and retries.
- When building AI agents or orchestrators that require stateful, multi-step execution.
- When integrating human approval steps into automated backend processes.
Advantages
- Eliminates the need to hold serverless functions open for long durations.
- Built-in support for retries, failure callbacks, and dead-letter queues.
- Seamless integration with popular serverless platforms like Vercel and Cloudflare Workers.
- Simplifies complex state management for asynchronous operations.
Usage examples
- “How do I define a basic two-step workflow using the Upstash SDK?”
- The agent provides a code snippet using the serve() function and context.run() to define sequential steps that persist across execution.
- “How can I trigger a workflow from my existing backend code?”
- The agent demonstrates initializing the Workflow Client with a QStash token and using the trigger() method to initiate the workflow URL.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/upstash/upstash-workflow-js/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip upstash-workflow-js.zip -d .agents/skills
Documentation by Upstash
Upstash Workflow SDK
Bundled docs and source
Before writing or debugging SDK code, check node_modules/@upstash/workflow/docs/ for bundled docs and node_modules/@upstash/workflow/src/ for readable TypeScript source. Read and search the relevant files when present; otherwise use the references in this skill.
Quick Start
The Upstash Workflow SDK lets you expose serverless workflow endpoints and run them reliably using QStash under the hood.
Install:
npm install @upstash/workflowDefine a simple workflow endpoint:
import { serve } from "@upstash/workflow";
export const { POST } = serve(async (context) => {
await context.run("step-1", () => console.log("step 1"));
await context.run("step-2", () => console.log("step 2"));
});Trigger it from your backend:
import { Client } from "@upstash/workflow";
const client = new Client({ token: process.env.QSTASH_TOKEN! });
await client.trigger({ url: "https://your-app.com/api/workflow" });Other Skill Files
These files contain the full documentation. Use them for details, patterns, and advanced behavior.
basics:
basics/serve – How to expose workflow endpoints.
basics/context – Full API for workflow
context(steps, waits, webhooks, events, invoke, etc.).basics/client – Using the Workflow client to trigger, cancel, inspect, and notify runs.
features:
features/invoke – Cross‑workflow invocation.
features/reliability – Retries, failure callbacks, and DLQ.
features/flow-control – Rate limits, concurrency, and parallelism.
features/wait-for-event – Notify and wait-for-event patterns.
features/webhooks – Webhook creation and consumption.
how to:
how-to/local-dev – Local QStash dev server (auto via
QSTASH_DEV=true) and tunneling.how-to/realtime – Realtime and human‑in‑the‑loop workflows.
how-to/migrations – Migrating workflows safely.
how-to/middleware – Adding middleware to workflows.
other files:
rest-api – Low-level REST endpoints for interacting with QStash/Workflow.
troubleshooting – Common debugging and environment issues.
agents – Using Workflow with agents, orchestrators, and automation patterns.
Files
- ATTRIBUTION.mdAdded by AutoGineer892 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md3.4 KiB
- agents.md6.7 KiB
- basics/client.md4.1 KiB
- basics/context.md5.1 KiB
- basics/serve.md2.4 KiB
- features/flow-control.md3.9 KiB
- features/invoke.md2.6 KiB
- features/retries-failures-reliability.md6.3 KiB
- features/wait-for-event.md2.8 KiB
- features/webhooks.md2.5 KiB
- how-to/local-dev.md5.0 KiB
- how-to/middleware.md4.7 KiB
- how-to/migrations.md4.8 KiB
- how-to/realtime.md4.8 KiB
- rest-api.md6.6 KiB
- troubleshooting.md4.8 KiB
basics/context.md
Workflow Context Basics
This skill documents all workflow context functions available inside a TypeScript workflow. It focuses on how these APIs behave, how their parameters interact, and common pitfalls when composing them into reliable long‑running workflows.
context.api
context.api provides typed integrations for OpenAI, Anthropic, and Resend. These calls behave like context.call but enforce the correct operation names and body types.
Key points
Each provider exposes a
.call(stepName, config)function.tokenis always required.The
operationfield selects the API method.bodymust match the provider's type definitions.Returns
{ status, body }.
Example (combined)
// OpenAI + Anthropic + Resend usage
const openai = await context.api.openai.call("openai chat", {
token: process.env.OPENAI_API_KEY!,
operation: "chat.completions.create",
body: {
model: "gpt-4o",
messages: [
{ role: "system", content: "Hello" },
{ role: "user", content: "Hi" },
],
},
});
const anthropic = await context.api.anthropic.call("anthropic message", {
token: process.env.ANTHROPIC_API_KEY!,
operation: "messages.create",
body: {
model: "claude-3-5-sonnet-20241022",
max_tokens: 1024,
messages: [{ role: "user", content: "Hello" }],
},
});
// Resend email
const email = await context.api.resend.call("send email", {
token: process.env.RESEND_API_KEY!,
headers: { "content-type": "application/json" },
body: {
from: "Acme <[email protected]>",
to: ["[email protected]"],
subject: "Welcome",
html: "<p>Hi!</p>",
},
});context.call
Performs an HTTP request with long execution windows (up to 12 hours). Always returns a response, even for non‑2xx status codes.
Important parameters
url: required.method: defaults toGET.headers: object.body: body as string.retries: number of retry attempts.retryDelay: retry delay expression as string or number (in milliseconds).flowControl: throttling config.timeout: seconds for each attempt.workflow: used only when invoking a workflow insideserveMany.
Example (showing most fields)
const response = await context.call("sync user", {
url: "https://api.example.com/user",
method: "POST",
headers: { authorization: `Bearer ${process.env.TOKEN}` },
body: JSON.stringify({ id: userId, name }),
retries: 3,
retryDelay: "pow(2, retried)", // exponential
timeout: 20,
flowControl: {
key: "user-sync",
rate: 5,
parallelism: 2,
},
});Pitfalls
Localhost requests fail unless tunneled.
context.cancel
Cancels the current workflow run.
Workflow is marked canceled, not failed.
failureFunctiondoes not run.No DLQ entry.
Example
const result = await context.run("check something", () => ...);
if (result.cancel) await context.cancel();context.createWebhook
Creates a reusable webhook URL for external systems.
Example
const { webhookUrl, eventId } = await context.createWebhook("create webhook");
// Use webhookUrl with an external servicecontext.invoke
Invokes another workflow (must be served under the same serveMany) and waits for its completion.
Key parameters
workflow: the workflow definition.body: becomesrequestPayloadof invoked workflow.headers: forwarded headers.workflowRunId: optional override.retries,retryDelay,flowControl: control invocation retry strategy.
Example
const { body, isFailed, isCanceled } = await context.invoke("invoke child", {
workflow: childWorkflow,
body: { id: 123 },
headers: { foo: "bar" },
retries: 2,
});context.notify
Notifies waiting workflows created via context.waitForEvent.
Example
const { notifyResponse } = await context.notify("notify step", "order-updated", {
status: "shipped",
});notifyResponse lists all workflows resumed by this event.
context.run
Runs custom synchronous or async logic as a step. Values must be JSON‑serializable.
Example
const user = await context.run("load user", () => getUser());
await context.run("process user", () => process(user));
// Running in parallel
const a = context.run("step A", () => foo());
const b = context.run("step B", () => bar());
await Promise.all([a, b]);Pitfalls
Returned class instances lose methods due to serialization. Rehydrate via
Object.assign(new Class(), data).
context.sleep
Pauses workflow execution for a duration. String or numeric seconds.
Example
await context.sleep("wait 1 day", "1d");context.sleepUntil
Pauses execution until a specific Date, timestamp, or parseable string.
Example
const ts = new Date(Date.now() + 1000 * 60 * 60);
await context.sleepUntil("wait until", ts);context.waitForEvent
Waits for an event (triggered by context.notify) or until timeout.
Example
const { eventData, timeout } = await context.waitForEvent("wait for update", "order-updated", {
timeout: "2h",
});Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
What our scanner noticed· Medium risk
- Possible data-exfiltration endpoints
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Upstash
- Publisher
- Upstash (Official)
- Source
- upstash/skills · skills/upstash-workflow-js · commit 9f9e3e5
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Upstash.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download upstash-workflow-js.zip