How Inngest Works

Learn the basics of Inngest

Using the Inngest SDK, you define your functions within your existing codebase and deploy your application anywhere. You define what events should trigger which functions and Inngest handles the rest.

Send events within your codeJobs run in your applicationStore full event historySchedule & enqueue jobsExecutes jobs and manages state

The lifecycle of a background job starts in your application with an event.

  1. Your application uses the Inngest SDK to send events within your code, for example, at the end of a user signup flow.
  2. Inngest receives the event and immediately stores the full event history for logging and future retries and replays.
  3. Inngest then determines if this event should trigger one or more of your functions and then schedules and enqueues jobs.
  4. Inngest then reads from the queue and executes jobs via HTTP and manages state across retries and multiple steps.
  5. Your application receives the request via the SDK's serve handler and the job runs in your application.

Ready to start building?

Ship background functions & workflows like never before

$ npx inngest-cli devGet started for free