ctdio/inngest-ctl
Overview
This skill provides a CLI interface for querying Inngest events and function runs. It lets you list and inspect events, send events with flexible payload options, monitor run status and duration, and cancel running functions. Use it to streamline debugging, local development, and production monitoring without handling raw HTTP requests or manual auth.
How this skill works
The CLI communicates with Inngest (or a local dev server) using configured environment keys for authentication and automatically builds requests and formats responses. Commands cover events (list, send, get, runs) and runs (status, get, list, cancel). Use the --dev flag to target a local development server and --pretty for human-readable output.
When to use it
- When you need to list recent or filtered Inngest events
- When you want to send test events or reproduce payloads
- When investigating function run status, duration, or step-level details
- When you need to list runs triggered by a specific event
- When you must cancel running functions across a time window
Best practices
- Always use the CLI rather than crafting manual HTTP requests—it handles auth, URLs, and output formatting
- Set INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY in your environment before running commands
- Use --dev and INNGEST_DEV_URL when testing against a local dev server
- Prefer heredoc or --data-file for complex JSON payloads to avoid escaping issues
- Use --pretty interactively and --output <file> when exporting JSON for analysis
Example use cases
- Debugging a failed workflow: list recent events, get event details, list runs for the event, then inspect run jobs
- Local development: run the local Inngest dev server, send a test event with --dev, and monitor the triggered run
- Production checks: list user.signup events with a limit and export results to JSON for auditing
- Automated cancellations: cancel runs for a function started within a time range using --started-after/--started-before
- Quick status checks: fetch run status and duration to confirm completion or identify stuck runs
FAQ
Set INNGEST_EVENT_KEY for sending events and INNGEST_SIGNING_KEY for API queries.
How do I target a local dev server?
Use --dev or set INNGEST_DEV_URL (and optionally --port) to point the CLI at your local server.