Inngest
Trigger durable functions and install event, retry, delay, and schedule workflows in a Swarmz project
Connect Inngest when a project needs work that must survive a request ending: background jobs, delayed steps, retries, event-driven functions, or schedules. Swarmz keeps the Inngest Event Key and Signing Key together as one shared connection.
Availability
A Swarmz administrator must show Inngest under Platform config > Integrations. Inngest does not require a Swarmz OAuth application. The workspace supplies keys for the intended Inngest environment.
Before you connect
Collect both values from the same Inngest environment:
- Event Key, used to send events.
- Signing Key, used by the generated serve endpoint to verify Inngest requests.
Inngest explains events and environment keys. Keep production and test environments in separate Swarmz connections.
Connect Inngest
- In the Swarmz project, open Settings > Integrations and select Inngest.
- Select Add connection.
- Paste the Event Key and Signing Key from the same environment.
- Select Save connection.
Swarmz encrypts both values. When the AI installs an Inngest serve function, it uses the exact project connection link to set INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY privately. The values do not enter chat or project source.
Available operations
| Operation | What it does | Limit per minute |
|---|---|---|
send_event | Sends one named event with bounded data, user, ID, and timestamp fields | 60 |
send_events | Sends a batch of up to 50 bounded events | 20 |
The AI can also install the Inngest SDK, client, functions, and one edge-function serve handler in the generated app. Event functions can use steps, sleeps, and retries; scheduled functions are defined in app code and served through the same handler. Inngest documents serving functions.
Ask the AI to use Inngest
- “When an order is created, send an
app/order.createdevent and run receipt and fulfilment steps with retries.” - “Build a welcome sequence that waits one day between messages and resumes after deployments.”
- “Add a daily cleanup function at 03:00 UTC and expose it through the Inngest serve endpoint.”
- “Send these imported records as one bounded event batch.”
The AI requests the connection before it writes the workflow. It uses send_event for real triggers and the project-side keys only when the app needs an Inngest serve handler.
Verify Inngest
- Send a uniquely named test event and confirm it appears in the intended Inngest environment.
- Install one disposable function that listens for that event.
- Trigger the event again and confirm the run and each step appear in Inngest.
- Force one retryable failure and verify the next attempt resumes correctly.
- Remove the disposable function and test event after verification.
Troubleshoot and recover
If events appear but no function runs, compare the event name exactly and confirm the deployed serve handler is registered in the same Inngest environment. If signature checks fail, reconnect with the Signing Key that belongs to the Event Key's environment.
To rotate keys, create a new pair in Inngest, replace both fields in the Swarmz connection, redeploy the serve function if required, and send a test event before revoking the old pair.