Skip to main content
Webhooks (/platform/webhooks) subscribes external systems to Forge platform events via HTTP POST with HMAC-SHA256 signing. It is the Webhooks tab of the Developers sidebar entry, after External Apps, Personal keys, and Forge MCP. Open it to add an endpoint, to check whether deliveries are reaching it, or to replay deliveries that failed.
Webhooks (dark)Webhooks (light)

Webhooks — Forge Console at /platform/webhooks

What you can do

  • Create Webhook opens a form with Endpoint URL (HTTPS required), Label (optional), Signing Secret (min 16 chars, used for HMAC-SHA256), and an event tree. Submit with Create Webhook; it stays disabled until the URL starts with https://, the secret has at least 16 characters, and at least one event is selected.
  • Click a subscription row to expand its health card and Recent Deliveries.
  • Send Test sends a test event to an active or paused subscription.
  • Edit changes Endpoint URL, Label (optional), and the subscribed events.
  • Pause stops sending events to an active subscription; Resume restarts a paused one.
  • Revoke permanently retires the subscription.
  • Replay in Recent Deliveries re-sends a delivered or failed delivery.
  • Replay in Dead-letter queue re-sends the original payload of a delivery that exhausted every retry.
Revoke acts on the first click, with no confirmation. A revoked subscription cannot be resumed, edited, or tested; create a new webhook to receive events again.

Statuses

Each row also shows the endpoint URL, the event count (or “all events”), and {n} failures when deliveries are failing in a row.

Health card

The expanded card shows Healthy or {n} consecutive failures, plus Last delivery, Delivered (24h), and Failed (24h). Counts are capped at the most recent 100 deliveries in the window, so treat them as a floor. A paused subscription with 10 or more consecutive failures reads “Auto-paused after consecutive delivery failures.”; any paused subscription shows a Resume button on the card.

Who can act

Listing subscriptions requires events:read; the subscription health card requires webhooks:read. Creating, pausing, resuming, and revoking require webhooks:manage.

Key state to watch

  • {n} failures on a row or an Auto-paused notice: the endpoint is rejecting or not answering. Fix the endpoint, Send Test, then Resume.
  • pending entries in the Dead-letter queue: those events never arrived. Replay them once the endpoint is healthy.
  • Failed (24h) above zero on a Healthy subscription: some deliveries failed in the last 24 hours, but the latest one succeeded.
  • A paused subscription nobody remembers pausing: events are not being sent; check its health card before resuming.