Integrations
Connect Sentry
Open errors of your Sentry projects appear in the projects, new ones immediately.
Where to connect
In VentionDesk under Workspace › Sources › “Add source”, category Errors, then Sentry. Only the owner may connect, edit and remove.
Step by step
- In Sentry, open Settings › Developer Settings › Custom Integrations and click “Create New Integration” › “Internal Integration”. Name: “VentionDesk”.
- Keep permissions as tight as possible: Project “Read”, Issue & Event “Read”, Organization “Read”, everything else “No Access”. This way VentionDesk only reads.
- For the “Resolved” button (in VentionDesk and for Claude with “Mark error as resolved”), set Issue & Event to “Read & Write” — that is the scope event:write. VentionDesk then first marks the error as resolved in Sentry and only afterwards on its side. Without this permission, VentionDesk only reads: “Resolved” then leaves the error open and tells you which permission is missing.
- Under “Webhooks”, tick “issue”. After saving, VentionDesk shows the webhook address under “Workspace” › “Sources” › Sentry; then enter it as the “Webhook URL”.
- Save the integration, copy the token under “Tokens” and the client secret under “Credentials”, and enter both here together with the organisation slug. VentionDesk checks the access by querying the open issues.
- VentionDesk fetches the open issues of the assigned projects every ten minutes; the webhook reports new and reopened ones immediately. Then, on the project page under “Analytics” › “Assign error source”, assign each project to its project at the provider.
- For each error, VentionDesk only takes the identifier, a shortened title (email and IP addresses in it are masked), level, status, number of events and affected users, first and last occurrence and the link to the provider. Stack traces, events, user data, IP addresses and requests stay with the provider and are not stored from webhooks either.
What the dialog asks for
| Field | Entry | Where from |
|---|---|---|
| API token | Required | secret | The token of the internal integration (Settings › Developer Settings › Custom Integrations › your integration › Tokens). |
| Organisation slug | Required | It is in the address: sentry.io/organizations/<slug>/ or <slug>.sentry.io. |
| Region | optional | “de” for accounts in the EU region (de.sentry.io), otherwise leave empty. Self-hosted Sentry servers are not supported. |
| Client secret | optional | secret | Only for the webhook: VentionDesk uses it to check the signature (Sentry-Hook-Signature). It is in the integration under “Credentials”. |
| Create tasks automatically | optional | “an” (default, on) or “aus” (off). On: an error that reaches the threshold or has the level “fatal” is created once as a task for Claude. |
| Threshold (events) | optional | The task is created from this many events. Leave empty for 10. |
VentionDesk stores secret entries encrypted and never shows them again. They are only saved once the provider confirms the access; if you edit a connection and leave a secret field empty, the previous value is kept.
All providers at a glance: IntegrationsWebhook URLs: Webhooks