Changelog

We are excited to announce the release of Realtime, a new feature that allows you to stream updates from your Inngest functions to your users.

Realtime is built upon Inngest's protocol, ensuring secure, low-latency and at-most-once delivery of messages.

Read more about the new Realtime APIs available in our TypeScript and Go SDKs in the release blog post.

We are thrilled to release Fetch, a set of new APIs to make durable HTTP requests within an Inngest function. Now available in our TypeScript SDK, the step.fetch() API and the fetch() utility enable you to make requests to third-party APIs or fetch data in a durable way by offloading them to the Inngest Platform.

const processFiles = inngest.createFunction(
  { id: "process-files" },
  { event: "files/process" },
  async ({ step }) => {
    // The request is offloaded to the Inngest Platform
    const response = await step.fetch("https://api.example.com/files", {
      method: "GET",
      headers: {
        "Authorization": `Bearer ${process.env.API_KEY}`
      }
    })

    // Your Inngest function is resumed here with the response
    await step.run("process-file", async (file) => {
      const body = await response.json()
      // body.files
    })
  }
)

Read more about the new Fetch APIs in the release blog post.

The old Events list in Cloud is now called Event Types, with improved usability!

You can now search by name and filter by status — active or archived.

Coming soon: A new Events stream page where you can view all received events in one place.

The CMD+K quick search in Cloud is now even more powerful!

In addition to searching by event and run ID, you can now find results by app, event, and function names, making it easier than ever to locate what you need in each environment.

We've also added quick access to useful pages (like signing keys) and top actions (such as adding an app), making navigation even faster.

Coming soon: the ability to view recent searches. What other actions would you like to access instantly? Let us know!

We're introducing a new run traces view!

The run traces view has been redesigned to better organize and visualize traces for complex workflows, especially Agentic AI workflows that may involve many steps with larger payloads and outputs.

Trace visualizations are now more interactive. You can drill into and expand individual run steps to see and work with inputs, outputs and errors.

If at any time you want to jump back to the legacy runs view there is a toggle to do that at the top of the view.

We're introducing a highly requested feature: dark mode!

You can now change your theme in the settings dropdown, and select between light, dark or your system preference.

Read more about the design and implementation process of this feature in the blog.

You can now export your Inngest metrics to Prometheus. This enables you and your team to use Inngest's metrics in your existing monitoring and alerting systems.

Several metrics are now available to export, including:

• inngest_function_run_scheduled_total
• inngest_function_run_started_total
• inngest_function_run_ended_total
• Read the full list of metrics in the docs.

To get started, visit the new Prometheus page in the "Integrations" section of the Inngest dashboard and follow the instructions to get the scrape config for the environment that you want to export metrics from.

It's available on all paid plans today. Read more information in the docs.

The new webhooks management API endpoints are now available as part of the Inngest REST API.

You can now create, update, and delete webhooks for your Inngest account, including updating transform functions. This enables you to:

• Manage webhook transforms within your codebase, including adding unit tests for your transforms.
• Programmatically create, update, and delete webhooks for customers or integrations.

To help you get started, we created a webhook transform sync demo repo that shows how you can test and sync transforms between your codebase and Inngest.

Read more information in the API docs.

You can now archive events in your Inngest environment. This is useful if you want to hide old events that you no longer use.

Archiving events does not prevent them from being received, they only hide them from your dashboard. If an archived event is received, it will be unarchived automatically.

Postgres support is now available for self-hosted Inngest. This enables you to use Postgres as your event storage backend, instead of the default SQLite. This will be marked as experimental until additional testing is completed and feedback is received.

Available in the Inngest CLI v1.4.0 with the --postgres-uri flag.

A new system event has been added to allow you to write functions that run after other function runs are cancelled. This enables you to handle cancelled runs gracefully.

• Example: Cleanup after function cancellation
• inngest/function.cancelled - System event reference