Sentry webhook source guide

Set up the webhook in Sentry

1. In Sentry, open Settings → Developer Settings → Custom Integrations and create an Internal Integration.
2. Set the Webhook URL to the endpoint's ingestion URL and subscribe to issue and alert resources.
3. Copy the Client Secret into the Hooks endpoint secret.
4. Enable Alert Rule Action if you want event_alert.triggered deliveries, then trigger a new issue.

Signature verification

• The resource comes from Sentry-Hook-Resource and the action from the body, combined as <resource>.<action>.
• occurredAt uses issue lastSeen (falling back to firstSeen) or alert event.datetime.
• project.slug (falling back to name) or event.project becomes project; level is kept on the subject.

Events Hooks normalizes

Normalized payload

Every adapter produces this shape before filters or templates run. The raw payload and sanitized headers stay attached for audit, but filters and templates read the normalized fields.

{
  "id": "evt_01j9m9g8h9",
  "source": "sentry",
  "type": "issue.created",
  "action": "created",
  "deliveryId": "9b1c7d3e-2a4f-4e8b-8c6d-1f0a2b3c4d5e",
  "occurredAt": "2026-11-01T09:33:08.000Z",
  "actor": { "type": "application" },
  "project": "checkout-web",
  "subject": {
    "kind": "issue",
    "id": "4509123456",
    "title": "TypeError: Cannot read properties of undefined",
    "url": "https://acme.sentry.io/issues/4509123456/",
    "body": "checkout.summary in app/checkout/summary.tsx",
    "state": "unresolved",
    "level": "error"
  }
}

Filter and template examples

{
  "allow": [
    { "field": "event.type", "op": "equals", "value": "issue.created" },
    { "field": "event.subject.level", "op": "in", "value": ["error", "fatal"] }
  ]
}

{
  "routineUrl": "https://grok.example.com/routines/abc123",
  "key": "{{secret.GROKBOT_KEY}}",
  "task": "Triage {{event.project}}: {{event.subject.title}}\n{{event.subject.body}}\n{{event.subject.url}}"
}

Retries and the delivery log

408, 425, 429, and 5xx responses retry with backoff and honor Retry-After; other 4xx responses fail permanently with a named code. Every attempt keeps the rendered request and the target response, so a failure points at one field or one status instead of a guess.

Common errors

Pair with a target

Reference

• Receiving eventshttps://hooks.events/docs/receive-events.md
• Verify signatureshttps://hooks.events/docs/signatures.md
• Payload templateshttps://hooks.events/docs/templates.md

Other sources