Inngest Events

This teaches Claude how to design event-driven workflows with Inngest's event system. You'll use it when building fan-out patterns where one event triggers multiple independent functions, implementing idempotency with event IDs (24-hour dedupe window), or handling webhooks from services like Stripe. It covers the event payload schema, the object-action naming pattern (like "billing/invoice.paid"), using the ts parameter for delayed delivery, and system events for monitoring function failures. The fan-out examples are solid, showing how to send a single event and have multiple functions respond independently with their own retry logic. TypeScript focused, but concepts apply across languages.

skills.sh installs: 4K
GitHub stars: 29
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add inngest/inngest-skills --skill inngest-events --agent claude-code

Installs into .claude/skills of the current project.

Files

Inngest Events

Master Inngest event design and delivery patterns. Events are the foundation of Inngest - learn to design robust event schemas, implement idempotency, leverage fan-out patterns, and handle system events effectively.

These skills are focused on TypeScript. For Python or Go, refer to the Inngest documentation for language-specific guidance. Core concepts apply across all languages.

Event Payload Format

Every Inngest event is a JSON object with required and optional properties:

Required Properties

type Event = {
  name: string; // Event type (triggers functions)
  data: object; // Payload data (any nested JSON)
};

Complete Schema

type EventPayload = {
  name: string; // Required: event type
  data: Record<string, any>; // Required: event data
  id?: string; // Optional: deduplication ID
  ts?: number; // Optional: timestamp (Unix ms)
  v?: string; // Optional: schema version
};