Trigger.dev icon

Trigger.dev

Trigger.dev provides hosted, code-defined webhooks for TypeScript apps—verifying, deduplicating, and routing events to tasks or AI agents.

Trigger.dev

Durable webhooks for TypeScript workflows

Trigger.dev provides hosted webhook endpoints declared in TypeScript. It receives events from customer-facing services, verifies and records each request, deduplicates deliveries, and routes accepted events into durable task and agent workflows.

A webhook can start a new run, wake a waiting run after an approval or external event, or add an event to an agent conversation. Developers can connect providers such as Slack, Linear, Stripe, GitHub, Shopify, Supabase, and services using Svix or Standard Webhooks, with setup managed through the Trigger.dev Webhooks page and endpoint configuration.

Webhook and agent workflow features

Code-defined endpoints

Declare hosted webhook endpoints in TypeScript and connect them to services that send event updates.

Request verification

Requests are verified using provider signing schemes. The product page documents Svix and Standard Webhooks support, while native Slack and Linear packages handle provider-specific verification and acknowledgment behavior.

Deduplication and delivery records

Incoming deliveries are deduplicated and recorded before they are routed, helping prevent repeated provider retries from starting duplicate work.

Start, resume, or message agents

A webhook can start a new task or agent run, resume a run paused for an approval or external event, or send an event into an agent conversation.

Filtered fan-out

Filter events and route one webhook to multiple subscribers; the product page shows one GitHub webhook starting up to 25 tasks or agents.

Slack and Linear agent packages

Use built-in Slack and Linear packages for agent interactions, including messages, mentions, approvals, streamed replies, plans, and provider-specific acknowledgments.

Practical webhook use cases

  • Automated code review

    Start an agent when a pull request opens, then have separate subscribers review the diff, label the pull request, scan for security issues, or deploy a preview.

  • Approval-based support operations

    Receive a Slack request, look up payments, ask for approval, wait for the decision, then update the subscription and confirm the refund in the same thread.

  • Billing and fraud workflows

    Use payment and commerce events to run billing workflows such as refunds, failed-payment handling, plan changes, or fraud review with a human approval step where needed.

  • Event-driven operations

    Wake an agent from an external event such as a PagerDuty alert, Sentry issue, Linear assignment, or a completed voice call so it can investigate, update records, or prepare a response.

  • Customer-facing automation

    Route customer conversations and lifecycle events from services such as Intercom, WhatsApp, or Clerk into agents that triage support, assist onboarding, or hand work to a human when appropriate.

Pros and Cons

Pros

  • Endpoints are declared in application code rather than managed only through a separate webhook service.
  • Verification, deduplication, and delivery recording are built into the webhook flow.
  • Events can trigger, resume, or message durable agent and task runs.
  • Filtering and subscriber fan-out support workflows where one event feeds multiple tasks or agents.
  • Native Slack and Linear packages cover provider-specific agent interaction patterns.

Cons

  • The available documentation does not establish a complete list of supported providers, webhook-specific limits, or all operational constraints.
  • Provider setup still requires registering the endpoint URL and configuring a signing secret; deliveries are rejected until an endpoint has a usable secret.
  • Cloud usage is subject to plan concurrency and API limits, and compute and run-invocation usage can add charges beyond included credits.

FAQ

How do I connect a webhook provider?

Declare a webhook endpoint in your TypeScript project, deploy the project or run `trigger dev`, then register the endpoint URL with the provider. Add the provider-issued signing secret, or generate one where supported, so Trigger.dev can verify deliveries. The Webhooks page and endpoint page provide setup prompts and endpoint details.

What can happen when a webhook arrives?

Trigger.dev webhook endpoints can start a new task or agent run, resume a paused run, or deliver an event to an agent conversation. Subscribers can filter events, and a single webhook can route an event to multiple subscribers.

Which webhook providers and integrations are supported?

The product page shows native packages for Slack and Linear, plus verification support for Svix and Standard Webhooks. It also lists integrations and examples involving services such as Stripe, GitHub, Shopify, Supabase, and Slack; availability and setup requirements depend on the provider.

How is Trigger.dev priced?

Trigger.dev Cloud plans include a Free tier with $5 in monthly compute credits and 20 concurrent runs. Paid plans are available, and usage also includes compute and run-invocation charges; the pricing page should be consulted for current plan details.

Quick Facts

Category
Developer Tool
Platform
TypeScript / Trigger.dev Cloud
Primary users
Developers building tasks, workflows, and AI agents
Core workflow
Receive, verify, deduplicate, record, and route webhook events
Native packages
Slack and Linear
Cloud availability
Free tier and paid plans; self-hosting is also available