inngest-setup

Automate Inngest durable execution setup in TypeScript projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inngest setup enables durable execution in TypeScript apps, allowing retry-safe webhook handlers, background jobs that survive crashes, and long-running workflows that outlive a single request.

Core Features & Use Cases

  • Install the Inngest SDK
  • Create a shared Inngest client
  • Configure environment variables for production and development
  • Expose serve endpoints for Next.js, Express, Hono, and Fastify
  • Use connect-as-worker mode for long-running processes
  • Run and debug locally with the Inngest dev server

Quick Start

Install the Inngest SDK, create a shared client, and configure environment variables to begin local development.

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 durable execution for background jobs in TypeScript?

Durable execution is set up by installing the Inngest SDK, creating a shared client, and configuring environment variables to handle background jobs and long-running workflows that survive crashes.

Can I use Inngest durable execution with an Express or Hono backend?

Yes, Inngest durable execution works with Express and Hono backends, alongside Next.js and Fastify, by exposing serve endpoints to handle webhook routing and background jobs.

How do I run and debug Inngest workflows locally in a dev server?

To run and debug Inngest workflows locally, you use the Inngest dev server which supports both serve and connect-as-worker modes for testing long-running processes before deployment.

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

Serve mode exposes HTTP endpoints for webhook handlers in frameworks like Next.js and Express, while connect-as-worker mode handles long-running processes without exposing public endpoints.

Why do I need a shared Inngest client for my TypeScript application?

A shared Inngest client centralizes SDK configuration and environment variables, ensuring retry-safe webhook handling and durable execution across your application's background jobs and workflows.

Do I need to configure environment variables for Inngest local development?

Yes, configuring environment variables is required for Inngest local development to properly route webhook handlers and background jobs through the local dev server before production deployment.