Skip to main content
Each endpoint verifies deliveries with one credential: a signing secret, or a public key for providers that sign with a key pair. Every delivery is rejected until the credential is set.

Set the credential

Each provider page says which one that provider needs.

Rotate a credential

Choose Rotate signing secret to replace a provider-supplied secret. For a secret you generate, choose Regenerate secret, copy the new value, and update the provider’s configuration. Use Rotate public key when replacing an asymmetric provider’s key. Both dialogs ask how long to keep accepting the old secret: Stop immediately, 1 hour, 24 hours (the default) or 7 days. Until then, deliveries signed with either secret verify, so you can update the provider without failing any. Choose Stop immediately if the old secret leaked. Through the MCP tools or the REST API, pass previousSecretTtlSeconds (at most 604800, 7 days). The response’s previousSecretExpiresAt says when the old secret stops working. Without it, the old secret stops working straight away:
Trigger.dev stores credentials encrypted and doesn’t display saved values. Copy a generated secret before closing the dialog.

Store secrets from the CLI

The CLI webhooks commands store a secret without printing it. Use them with AI agents that can run shell commands: a secret passed to set_webhook_secret, or returned by generate_webhook_secret, becomes part of the agent’s conversation, and the MCP tool descriptions point agents to the CLI instead.

MCP tools

The Trigger.dev MCP server (npx trigger.dev@latest install-mcp) has these webhook tools:

REST API

The same operations are available on the REST API with the environment’s secret key: endpointId is the endpoint’s declared id (the id passed to webhooks.endpoint.define) or its wh_ id, shown on its page and returned by list_webhook_endpoints: