Jasper + Sentry: errors next to the repositories you review
Connect Sentry with an auth token, map each Sentry project to its GitHub repository, and Jasper turns the issue events Sentry sends into a seven-day error summary for each project.
What you can do
- Record which Sentry project belongs to which client repository.
- See new issues, resolved issues and fatal errors for each mapped project over the last seven days.
- See every Sentry webhook Jasper received, and whether its signature was valid, on the webhook history page.
What syncs
| Data | Direction | When |
|---|---|---|
| Your Sentry organisation and its projects | Sentry → Jasper | When you connect. Projects are read again when you click Sync Projects and when you open Repository Mappings. |
| Issue and error events | Sentry → Jasper | As they happen, by signed webhook. New and resolved issues in mapped projects build the error metrics. |
| Unresolved issues seen in the last 24 hours, up to 100 per project | Sentry → Jasper | Hourly. Stored in Jasper but not shown yet. |
| Issue status | Not synced | Resolving or ignoring an issue from Jasper isn't available yet. |
Set up in 5 steps
Who can do this: Owners and admins of your Jasper organisation, with a Sentry auth token and access to create an internal integration in Sentry.
- In Jasper, open Settings, then All Integrations, click Connect Sentry, then Enable Sentry Integration.
- In Sentry, create an auth token with org:read, project:read and event:read. Paste it into Sentry API Token and click Connect to Sentry.
- On the Repository Mappings page, map each Sentry project to its GitHub repository.
- On the Webhooks page, copy the webhook URL. In Sentry, create an internal integration with that URL, Issue & Event read access and the issue and error webhooks.
- Copy the integration's client secret from Sentry, paste it into Client Secret in Jasper and save.
Permissions we ask for, and why
Sentry calls the issue scopes event:read and event:write. Jasper only reads from Sentry today.
| Permission | Why Jasper needs it |
|---|---|
org:read |
Find your Sentry organisation when you connect. |
project:read |
List your projects so you can map them to repositories. |
event:read |
Read each project's unresolved issues in the hourly sync. |
Internal integration: Issue & Event read, with issue and error webhooks |
Lets Sentry send issue and error events to Jasper. Jasper rejects any webhook not signed with the client secret you saved, so nothing is accepted until you save it. |
Your data
- Your Sentry auth token and the integration's client secret are stored encrypted.
- Jasper stores the webhook events it receives, including rejected ones, with their headers, sender IP address and the issue details in them, and up to 100 unresolved issues per project from the hourly sync.
- Disconnecting deletes the auth token. Mappings, the client secret, received events and metrics stay in Jasper, and metrics stop updating. Remove the internal integration in Sentry to stop the webhooks.
Our privacy policy covers what we store, where, and for how long.
Limits and what is not synced
- This integration is in beta.
- Resolving or ignoring Sentry issues from Jasper isn't available yet, and Jasper doesn't show links between Sentry issues and pull requests.
- Jasper doesn't create ClickUp tasks from Sentry issues, and doesn't pass Sentry alerts on to email or chat.
- Metrics come only from webhooks, so they start when you add the internal integration and don't include older events. They count only Sentry projects mapped to a repository.
- One Sentry organisation per workspace: the first one the token can see. Jasper works with sentry.io, not self-hosted Sentry.
Common questions
Can I resolve Sentry issues from Jasper?
Not yet. Today Jasper only reads from Sentry.
Why do I need an internal integration as well as a token?
The token lets Jasper read your organisation, projects and issues. The internal integration is how Sentry sends Jasper events as they happen, signed with its client secret.
What happens to a webhook without a valid signature?
Jasper rejects it. Until you save the client secret, Jasper rejects every webhook.
Does it work with self-hosted Sentry?
No. Jasper connects to sentry.io.
Which plan includes Sentry?
Every plan. It is free during the beta.
Guides
Works with
Other integrations
Checked against the product on 4 October 2026. Sources: Sentry docs, permissions and scopes.