Webhooks and event-based triggering
Hatchet is built for modern, event-based architectures. Events are a first-class primitive in Hatchet, and you can subscribe to any event for workflow triggering, pause-and-resume, and human-in-the-loop behavior.
Event-based triggers
Define your workflows to trigger based on events sent from your system or produced by a webhook.
One event, many workflows
Individual events can trigger multiple downstream steps or tasks. Fan a single event out to every workflow that subscribes to it, and use event filters to route payloads to exactly the right runs.
Push an event once — every workflow subscribed to its key gets its own run.
Built-in webhook ingestors
Point third-party webhooks straight at Hatchet. Pre-configured sources for Stripe, GitHub, Slack, Linear, and Svix need only a signing secret — and generic sources integrate any sender, with CEL expressions turning each payload into a routable event key.
Webhooks create Hatchet events after validation, which can trigger or resume any downstream workflow.
Viewable event history
Each task ships with a debuggable event log, as well as a top-level user event log for debugging. See exactly which events arrived, when, and which runs they triggered.
Every event, trigger, and state change is logged and queryable in the dashboard.
Build event-driven systems on Hatchet. Every event tracked, every trigger durable.
Start for free — no credit card required
Processing over 100 million tasks/day on Hatchet Cloud
Open-source and self-hostable