Skip to main content
A webhook endpoint is one hosted URL that you register with a provider. Trigger.dev verifies every request from the provider, records it as a delivery, and hands the event to everything subscribed to the endpoint. Webhooks can start, resume or message your AI agents.
Webhooks are in public beta for every organization, in @trigger.dev/sdk 4.8.1 and later. The API may change before general availability; we announce changes in the changelog. Send bugs and feedback to eric@trigger.dev with the delivery id (whd_...) or run id.
There are more than 40 built-in providers, including Stripe, GitHub, Firecrawl and Linear. For any other provider, define a custom provider. If you prefer to handle webhooks in your own app, you can trigger tasks from your own handler. To set one up from scratch, follow the quick start. Declare the endpoint once, then subscribe to it:
/trigger/stripe.ts
Stripe gets one URL. A checkout event runs fulfill-order, a refund runs record-refund, and anything else is recorded as FILTERED.

What can subscribe

Each subscriber has its own filter, so one delivery can reach several subscribers and skip the rest. An endpoint can have up to 25 tasks, agent sessions and channels subscribed; waiting runs don’t count toward that limit. An endpoint with no subscribers still gets a URL, so you can register it with the provider before writing the handlers. See Webhook tasks for what a handler receives and the options it takes.

Quick start

Declare an endpoint and receive your first event.

Providers

Set up more than 40 providers, including Stripe, GitHub and Firecrawl.

How it works

What happens to a request, from verification to runs.