Sentry Integration
Dispatch integrates with Sentry to receive webhook events for issues, errors, alerts, and AI autofix (Seer) activity.
Connecting Sentry
Sentry webhooks are sent from a custom Sentry integration (internal app). To set up:
- In your Sentry organization, go to Settings → Developer Settings → New Internal Integration
- Under Webhooks, enable the resource types you want (Issues, Errors, Comments, etc.)
- Set the Webhook URL to your Dispatch endpoint URL
- Copy the Client Secret shown on the integration page — this is your signing secret
- Create a Dispatch source with
provider = sentryand paste the signing secret into the Signing Secret field
Dispatch auto-detects Sentry payloads by the presence of the sentry-hook-resource header, so no manual provider selection is required.
Supported Sentry Events
The event type is extracted from the sentry-hook-resource header combined with the action field in the payload (e.g., issue.created, metric_alert.critical).
| Resource | Actions |
|---|---|
| Issues | created, resolved, assigned, ignored, archived, unresolved, deleted |
| Errors | created |
| Metric Alerts | critical, warning, resolved |
| Issue Alerts | triggered |
| Comments | created, updated, deleted |
| Installation | created, deleted |
| Seer (AI Autofix) | root_cause_started, root_cause_completed, solution_started, solution_completed, coding_started, coding_completed, pr_created |
Signature Verification
Sentry signs webhook payloads with HMAC-SHA256. The signature is sent in the sentry-hook-signature header. Dispatch verifies this automatically when a signing secret is configured on the endpoint.
sentry-hook-signature: <hmac-sha256-hex>
sentry-hook-resource: issue
If no signing secret is configured the signature check is skipped — useful for local development, but not recommended for production.
Auto-Formatted Embeds
When no custom template is assigned, Dispatch auto-detects Sentry payloads and generates specialized embeds:
Issue Events
- Shows the short ID, error title, culprit location, level, status, and priority
- First seen / last seen timestamps
- Color-coded by severity: red (error/fatal), orange (warning), blue (info), gray (debug/archived), green (resolved)
Error Events
- Shows exception type and value, culprit location, platform, and linked issue
- Color-coded by severity level
Metric Alert Events
- Shows alert rule name, trigger description, affected projects, metric aggregate, and time window
- Color-coded: red (critical), orange (warning), green (resolved)
Issue Alert (Event Alert) Events
- Shows the alert rule name that fired, the triggering error title and culprit, and the linked issue
- Orange color to indicate an active alert
Comment Events
- Shows the comment text (truncated), author, and linked issue ID
- Blue for created/updated, gray for deleted
Seer AI Autofix Events
- Tracks each stage of the Seer autofix pipeline
- For completed stages, shows the root cause description, solution summary, or code changes with branch names and PR links
Disconnecting
To stop receiving Sentry webhooks:
- In your Sentry integration settings, remove or disable the webhook URL
- In Dispatch, deactivate or delete the endpoint