AutoGineer
Generated banner for Upstash Workflow JS
Generated logo for Upstash Workflow JS

Upstash Workflow JS

UpstashOfficialCreated by Upstash

  • Skill
  • Tool integration
  • Cloud and DevOps
  • MIT
  • Medium risk
Download ZIP

From the author

Work with the @upstash/workflow TypeScript/JavaScript SDK for durable, long-running workflows in serverless functions, multi-step processes that survive timeouts, retries, and restarts (built on QStash). Use when defining a workflow endpoint with serve(), running steps with context.run, sleeping for minutes to days without holding a function open, calling external APIs with context.call, waiting for an external event or webhook, invoking other workflows, configuring retries, failure callbacks, and a DLQ, controlling concurrency, rate, and parallelism, triggering, cancelling, or inspecting runs with the Workflow client, building AI agents and orchestrators, human-in-the-loop approvals, realtime updates, local development with the QStash dev server, adding middleware, or migrating workflows safely. Also use when the user asks for durable execution, step functions, saga or orchestration patterns, background jobs with checkpoints, or long-running tasks on Vercel, Next.js, Cloudflare Workers, or other serverless
— the description by Upstash

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

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/upstash/upstash-workflow-js/download

  2. Unzip 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/workflow

Define 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

features/invoke.md

Workflow Invocation

This documentation covers how to invoke one workflow from another using context.invoke, along with how to define and expose multiple workflows using createWorkflow and serveMany.

Invoking Another Workflow

A workflow can start another workflow run and wait for it to finish before continuing. This enables orchestration and dependency chains across workflows.

Use context.invoke to trigger another workflow:

const result = await context.invoke("analyze content", {
  workflow: analyzeContent, // workflow object or function
  body: "input payload", // request body passed to invoked workflow
  headers: { "x-user": "123" }, // optional headers
  retries: 5, // optional, default 3
  flowControl: {
    /* ... */
  },
  workflowRunId: "optional-custom-id",
});

const {
  body, // response returned by invoked workflow
  isFailed, // true if invoked workflow failed
  isCanceled, // true if invoked workflow was canceled
} = result;
Returning a Value

A workflow may return any serializable value, which becomes body for the caller.

Depth Limitation

Workflow invocation depth is limited to 100. Any recursive or cyclic chain exceeding this will fail.

Defining Workflows Without Exposing Endpoints

Use createWorkflow to define workflows as objects. These are not automatically exposed as HTTP endpoints.

const analyzeContent = createWorkflow(async (context) => {
  await context.sleep("delay", 1);
  return { message: "processed" };
});

const processUser = createWorkflow(async (context) => {
  const { body } = await context.invoke("invoke analyze", {
    workflow: analyzeContent, // type‑safe invocation
    body: "user-1",
  });

  return { result: body };
});

Exposing Multiple Workflows With serveMany

To allow workflows to invoke each other without requiring explicit URLs, define all related workflows under a shared parent path.

// app/workflows/[...any]/route.ts
export const { POST } = serveMany({
  analyze: analyzeContent,
  process: processUser,
});

  • Keys become route names.

  • All workflows that need to invoke each other must appear in the same serveMany call.

  • Requests are routed based on the key names.

Triggering a Workflow
import { Client } from "@upstash/workflow";

const client = new Client({ token: "<QSTASH_TOKEN>" });

await client.trigger({
  url: "https://your-app/workflows/analyze",
});

Common Pitfalls

  • Missing workflow in serveMany: If a workflow invokes another that was not included in the same serveMany definition, the call will fail.

  • Infinite invocation loops: Depth limit of 100 prevents runaway recursive chains.

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 or Upstash.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download upstash-workflow-js.zip