Sentry Integration
Auto-create issues from error reports and link stack traces.
Setup
The Sentry integration uses a guided setup wizard instead of OAuth. Go to Settings → Integrations, click Connect on the Sentry card, and follow the three-step wizard:
Enter Auth Token
Generate an Internal Integration auth token in your Sentry organization settings. Paste it into Velocity along with a client secret for webhook signature verification.
Select Organization
Enter your Sentry organization slug (e.g., acme-corp). Velocity verifies the connection by fetching your organization details via the Sentry API.
Select Project
Choose which Sentry project to monitor. Velocity fetches your project list and lets you pick one. You can also map multiple Sentry projects to different Velocity teams later.
Automatic Issue Creation
When enabled, Velocity automatically creates a new issue whenever Sentry reports an error. The issue includes:
- Error title with
[Sentry]prefix - Stack trace, platform, and metadata in a rich Tiptap description
- Direct link back to the Sentry issue
- Priority mapped from Sentry severity level
Priority Mapping
Sentry severity levels map to Velocity priorities:
| Sentry Level | Velocity Priority |
|---|---|
fatal | Urgent |
error | High |
warning | Medium |
info | Low |
Deduplication
If the same Sentry issue fires again, Velocity recognizes the duplicate and updates the existing linked issue instead of creating a new one. The issue description is refreshed with the latest occurrence data.
Reopening Closed Issues
When a Sentry error recurs for a previously resolved Velocity issue, the behavior depends on your settings:
- Reopen (default) — The closed issue is reopened with its status reset to the team default
- Create new — A brand new Velocity issue is created instead
Status Sync
Enable Sync resolved status to keep Velocity and Sentry in sync. When an issue is resolved in Sentry, the linked Velocity issue is moved to the completed status. When reopened in Sentry, the Velocity issue is set back to its default status.
Project Mapping
Map Sentry projects to specific Velocity teams and projects. When an error comes in from a mapped Sentry project, the auto-created issue is assigned to the correct team automatically.
Webhook Configuration
Point your Sentry webhook to:
https://velocity.quest/api/webhooks/sentryThe integration verifies incoming webhooks using HMAC-SHA256 signature validation against the client secret you provided during setup. Events processed:
issue— New issue alertserror— Individual error eventsevent_alert— Alert rule triggersmetric_alert— Metric alert thresholds
Test Connection
The settings page includes a Test Connection button that verifies your auth token and organization slug by making a test API call to Sentry. Use this to confirm your setup before saving.