Inngest
Give the Sazabi agent the Inngest CLI (inngest) in its sandbox to inspect Inngest Cloud runs, functions, deployments, and events.
About
This CLI connection makes the Inngest CLI (inngest) available in the Sazabi agent's sandbox. The agent can use it for inspecting Inngest Cloud runs, functions, deployments, and events. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- An Inngest API key (
INNGEST_API_KEY), available from your Inngest Cloud dashboard. - Optionally, an Inngest event key (
INNGEST_EVENT_KEY) if you need to send or inspect events.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Inngest in the catalog
In Settings > Sandbox CLIs, find Inngest under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: INNGEST_API_KEY — your Inngest Cloud API key. Optionally, provide INNGEST_EVENT_KEY to enable event operations. Save to store them securely; Sazabi injects them into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Inngest CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type inngest --env INNGEST_API_KEY=<your-inngest-key>To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).
Verify
Ask the agent, in a thread, to run the inngest CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.
Troubleshooting
Command not found — Confirm the Inngest CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.