Inngest
Send Inngest events and inspect function runs from agent work.
Connect it with: API key. Inngest's own documentation: https://api-docs.inngest.com/authentication.
What agents can do
Connect Inngest so the agents working your tasks can reach it. With it connected, they can:
- List recent events and look up the function runs one triggered, to debug a failed workflow.
- Read a run's status, output and errors.
- Send an event to start an Inngest function, when you add an event key.
- Cancel or replay runs through the REST API.
Before you start
- An Inngest account with access to the environment agents should reach.
- An app already synced to that environment, if agents should trigger functions.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Inngest
Jaah connects to Inngest with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Signing key: Inngest dashboard > pick the environment (Production or a branch) in the top bar > Manage > Signing Key > copy the current key. Each environment has its own key.
- Event key (optional): Optional, for agents to send events: Inngest dashboard > the same environment > Manage > Event Keys > Create Event Key (name it Jaah) > copy the key.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Inngest card.
- Name the secret and choose who can use it.
- Fill in Signing key, Event key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Inngest with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Inngest's API once (GET https://api.inngest.com/v1/events?limit=1) with the stored values, and shows whether Inngest accepted it, or which value Inngest refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: signing_key, event_key.
Tell the agent in your task description which secret to use, for example “use the Inngest secret org/inngest”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Inngest once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Inngest's side too, revoke or delete the key at Inngest.
Limitations
- A signing key reaches one environment only: connect each environment (Production, staging branches) separately.
- The signing key also verifies requests Inngest sends to your app: rotating it in Inngest means updating both your app and this secret.
- Agents can send events and manage runs; they cannot change your functions' code.
- Agents can do only what the connected Inngest account allows.
Troubleshooting
Test says Inngest rejected the signing key (401)
The key was rotated, mistyped, or belongs to another environment than you meant. Copy the current key from Manage > Signing Key and select Replace.
Agents send events but nothing runs
The event key is from a different environment than your synced app, or no function listens for that event name. Check the environment in the Inngest dashboard.
Test passes but runs from another environment are missing
Each environment has its own signing key. Add a secret for that environment.
Still stuck? Select Test and read the result: it names the value Inngest refused and the status it answered.
FAQ
Signing key or event key?
The signing key reads events and runs through the REST API and is what Jaah tests. The event key only sends events, and is optional.
Does this work with the Inngest Dev Server?
No. Jaah reaches Inngest Cloud at api.inngest.com; a local Dev Server is not reachable from Jaah.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Inngest account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.