Sentry webhook intake
Wire Sentry's "issue alert" webhook to a Lithify intake and new errors land in your inbox as briefs. The Sentry title becomes the brief title, the formatted exception becomes the description, the alert level becomes the priority, and the link back to Sentry stays on the brief.
Signed webhook Pre-classified as bug De-duplicated
Setup
- Open Project → Intakes and create an intake of type Sentry webhook. Lithify gives you a URL.
- Set a webhook secret. Lithify uses it to verify every incoming request.
- In Sentry, create an alert rule (or internal integration) that posts new issues to that URL.
- Pick a default brief type for the intake — usually bug.
How Sentry maps onto a brief
| Sentry | Brief |
|---|---|
| Title or message | Brief title |
| Exception + the failing line of source | Brief description |
| Alert level | Brief priority (see below) |
| Environment, release, platform | Stored as labels and on the brief for context |
| Link to the Sentry issue | Surfaced on the brief detail page |
Level → priority
| Sentry level | Brief priority |
|---|---|
| Fatal | Critical |
| Error | High |
| Warning | Medium |
| Info / Debug | Low |
De-duplication. If Sentry keeps firing for the same issue, Lithify attaches subsequent events to the existing brief rather than creating new ones, so a noisy alert rule doesn't drown your inbox.