Skip to main content
webhooks.custom() verifies any provider that signs or authenticates its webhooks with one of four supported schemes. Use it when the provider isn’t in the built-in providers. Subscribers, filters, deliveries and the setup prompt work the same as with a built-in provider.

Define a custom provider

Pass the verification configuration to webhooks.custom(). This source verifies an HMAC-SHA256 signature over the raw body in x-webhook-signature and uses the event’s id for deduplication:
/trigger/internal.ts
To accept a signature from more than one header, list the extra headers in additionalSignatureHeaders (up to 4). Trigger.dev parses each one like signatureHeader and accepts a match in any of them. Use this when a provider sends a second signature, for example one signed with the previous secret during a rotation. signatureHeader is still required. The built-in hookdeck() source already checks X-Hookdeck-Signature-2 this way. The optional setupPrompt is the provider-specific part of the endpoint’s setup prompt: where the provider’s webhook settings are and how to register a URL there. Trigger.dev adds the URL, the subscribers’ filters and the signing secret steps around it.

Form-encoded bodies

A verified body sent as application/x-www-form-urlencoded reaches subscribers as an object of its fields, so filters, chat.event keys and waiter match paths read form fields the way they read JSON fields. A repeated field becomes an array of its values. Slack slash commands and other providers that post forms work this way. By default an accepted request gets a 200 with a small JSON receipt. Some providers show the response body to the user who triggered the request, so pass response: { acceptedBody: "empty" } to answer with an empty 200 instead:
/trigger/forms.ts

Verification schemes

webhooks.custom() supports these schemes:
Query parameters can appear in access logs, proxies, and traces. Prefer a header-based scheme when the provider supports one.