inngest-setup

Configures Inngest durable execution in TypeScript projects with serve endpoints and worker connections.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/firstaxel/neon --skill inngest-setup-firstaxel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inngest-setup
Source: https://github.com/firstaxel/neon/tree/main/.agents/skills/inngest-setup
Command: npx skills add https://github.com/firstaxel/neon --skill inngest-setup-firstaxel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires inngest.

What problem does it solve? Setting up durable execution for background jobs, scheduled tasks, and long-running workflows requires correctly wiring SDK installation, client configuration, environment variables, and framework-specific serve endpoints, where misconfiguration causes silent 500 errors and failed registrations. ## Core Features & Use Cases - Client and Environment Setup: Creates a typed Inngest client with event schemas, dev-mode flags, and signing key configuration via environment variables. - Connection Modes: Covers both HTTP serve endpoints (Next.js, Express, Hono, Fastify, Lambda, Cloudflare) and WebSocket connect-as-worker mode for long-running containers. - Local Dev Server: Guides running the inngest-cli dev server with auto-discovery, custom ports, and multi-app URLs. - Use Case: You need a retry-safe webhook handler in a Next.js app. This Skill walks you through installing the SDK, creating the client, exposing /api/inngest, and verifying registration in the local dev server. ## Quick Start Set up Inngest in my TypeScript project with a serve endpoint and local dev server configuration.

Frequently Asked Questions about inngest-setup

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

FAQPage Schema
How do I set up Inngest in a Next.js project?▼

Install the inngest package, create an Inngest client with a unique app id, then expose a serve endpoint at /api/inngest using inngest/next for App Router or Pages Router. Set INNGEST_DEV=1 for local development so the endpoint does not fail in Cloud mode.

Why does my Inngest endpoint return a 500 internal server error?▼

The 500 error occurs because Inngest v4 defaults to Cloud mode and no signing key is found. Set the INNGEST_DEV=1 environment variable for local development, or provide INNGEST_SIGNING_KEY for production Cloud mode.

What is the difference between Inngest serve and connect modes?▼

Serve mode exposes an HTTP endpoint suited for serverless platforms like Vercel and Lambda. Connect mode uses a persistent WebSocket for long-running containers on Kubernetes or Docker, requiring Node.js 22.4+ and supporting worker concurrency limits.

How do I run the Inngest dev server locally?▼

Run npx inngest-cli@latest dev to auto-discover your app on common ports, or pass -u http://localhost:3000/api/inngest to specify the URL manually. The dev server runs at http://localhost:8288 by default and reloads when functions change.

Does Inngest support typed events with validation?▼

Yes, the eventType helper accepts a Zod schema to define typed events. These event types provide full type safety both when triggering functions and when sending events via inngest.send.