upstash/qstash-js

Overview

This skill explains how to use the QStash JavaScript/TypeScript SDK to publish HTTP messages, create schedules, manage queues, and verify incoming webhook signatures in serverless or edge environments. It focuses on practical usage patterns, supported platforms, and integration points for reliable message delivery and processing. The content highlights when to use publishing, scheduling, FIFO queues, and receiver verification.

How this skill works

The SDK exposes a Client for publishing JSON or raw payloads to HTTP endpoints or URL groups, and a Receiver utility to verify incoming QStash signatures. It supports schedule creation, delayed delivery, FIFO queues with configurable parallelism, callbacks, and DLQ management. The library runs in Node, edge runtimes (Vercel, Cloudflare), Deno, and common frameworks like Next.js and SvelteKit. Use environment variables for tokens and signing keys and the SDK methods for publish, schedule, and queue operations.

When to use it

• Publish HTTP messages to third-party or internal endpoints reliably from serverless functions
• Create scheduled tasks or delayed job delivery without maintaining a separate scheduler
• Process ordered workloads with FIFO queues and controlled concurrency
• Verify incoming webhook requests from QStash to ensure authenticity
• Implement callbacks, dead-letter queues, or deduplication for robust message handling

Best practices

• Always verify incoming messages using the Receiver class and signing key stored in environment variables
• Keep QStash tokens and signing keys in secure environment variables, never in source code
• Set sensible retry counts, timeouts, and use DLQ for persistent failures
• Use queues plus limited parallelism to maintain order and avoid overloading downstream systems
• Prefer URL groups for broadcasting to multiple endpoints and use schedules for recurring tasks

Example use cases

• Send user-created events to a webhook reliably from an API route or edge function
• Schedule nightly report generation or email digests with delayed message delivery
• Create an ordered task queue for image processing with parallelism set to match workers
• Verify QStash-sent webhooks in a Next.js or Cloudflare Worker using Receiver before processing
• Route failed messages to a DLQ and implement a retry-and-inspect workflow for debugging