add-inngest-function

To scaffold an Inngest function for event-driven background processing, create a function file under api/src/inngest/functions, register it in api/src/inngest/index.ts, and run the local dev server to test. It enforces explicit retries, concurrency, logging, and idempotent step patterns.

Inngest functions support event-driven, cron, and cancellable triggers for flexible workflows. You can use step.run, step.sleep, and step.waitForEvent patterns to coordinate tasks across steps for scheduled maintenance jobs or webhook listeners.

You test Inngest functions locally by running the local dev server after creating the function file and registering it in api/src/inngest/index.ts. This covers local development and production-like environments to ensure reliable, debuggable workflows.

Idempotent step patterns are needed in event-driven workflows to ensure reliable, debuggable processing during retries. The scaffolding enforces explicit retries, proper concurrency, and logging alongside idempotent steps to handle background jobs and webhook listeners safely.

Yes, you can use step.sleep and step.waitForEvent to coordinate tasks across steps in Inngest. These patterns, along with step.run, enable flexible workflows for background processing, scheduled maintenance jobs, and webhook listeners within your TypeScript project.

The best way to structure webhook listeners in a TypeScript workflow system is using Inngest functions placed under api/src/inngest/functions, registered centrally in index.ts, leveraging event-driven triggers with idempotent steps and explicit retries for reliable processing.