Lawhive previews / dashboards / inngest

Inngest across the estate

Every Inngest event and function across platform-v3, platform-v2, and ai-platform (TypeScript and Python), with the chains between them resolved across repo boundaries. Events and functions are the foundation; each shows its proposed normalized name inline.

Generated27 July 2026 at 09:52 inngest-registry.json the complete package
An event is a named message. Emitted from is where it's sent (an Inngest function, or plain service/app code); consumed by is the functions it triggers. Every tag links to that exact line of source. Under each name is its proposed normalized name. Hover the Kind and flag chips for what they mean.
A function is an Inngest handler. Its name links to the definition (hover for the path); the triggered by and emits tags link to source. Under each name is its proposed normalized id.
A chain flows top to bottom: an event triggers a function, which emits more events, and so on — across repos. Pick a root event and switch to Graph to see everything reachable from it.
event a message function a handler