Sentry

Map your Sentry projects to GitHub repositories and see a week of error metrics in Jasper.

What it does

The Sentry integration is in beta and free while it is. It has two parts:

An auth token lets Jasper read your Sentry organisation, its projects and their unresolved issues.
An internal integration in Sentry sends Jasper issue and error events as they happen. Jasper builds a seven-day summary for each project from these events.

Jasper only reads from Sentry today. You can't resolve or ignore Sentry issues from Jasper yet, and Jasper doesn't show links between Sentry issues and pull requests.

Before you start

You need to be an owner or admin of your Jasper organisation.
In Sentry, you need to be able to create an auth token and an internal integration for your organisation.
Jasper connects to sentry.io. Self-hosted Sentry isn't supported.

1. Turn on Sentry and connect

In Jasper, open Settings → All Integrations and click Connect Sentry.
Click Enable Sentry Integration.
In Sentry, create an auth token with these scopes: org:read, project:read and event:read.
Paste it into Sentry API Token and click Connect to Sentry.

Jasper connects to the first Sentry organisation the token can see. Sentry calls the issue scopes event:read and event:write (Sentry's permissions and scopes, checked 4 October 2026). Jasper only needs event:read.

2. Map projects to repositories

Open the Repository Mappings page and choose the Sentry project for each GitHub repository. Each repository maps to one Sentry project.

If ClickUp is connected, the mapping form also has Link to ClickUp (Optional). It also has Auto-link issues and Error notifications. None of them changes anything you can see yet: Jasper doesn't create ClickUp tasks, doesn't show issue links on pull requests, and doesn't send error notifications. You can leave them as they are.

3. Add the internal integration

On Jasper's Webhooks page, copy the Webhook URL. It is unique to your organisation.
In Sentry, open Settings → Developer Settings → Custom Integrations and create a new internal integration.
Name it (for example, Jasper) and paste the webhook URL.
Under permissions, give Issue & Event read access.
Under webhooks, tick issue and error.
Save, then copy the integration's Client Secret.
Back in Jasper, paste it into Client Secret and save.

Once the client secret is saved, Jasper checks every webhook's signature against it and rejects any that don't match. Until it is saved, Jasper rejects every webhook. The Webhook History page lists what Jasper received, and whether each signature was valid.

Error metrics

The Error Metrics page shows new issues, resolved issues and fatal errors for each Sentry project mapped to a repository, over the last seven days. The numbers come only from webhooks, so they start when you add the internal integration. The Total Events figure stays at zero for now, because Jasper doesn't yet read the project from Sentry's error webhooks.

What syncs

Data	Direction	When
Organisation and projects	Sentry → Jasper	When you connect. Projects again when you click Sync Projects and when you open Repository Mappings
Issue and error events	Sentry → Jasper	As they happen, by signed webhook
Unresolved issues seen in the last 24 hours, up to 100 per project	Sentry → Jasper	Hourly; stored but not shown yet
Issue status	Not synced	Jasper doesn't change issues in Sentry

Your data and disconnecting

The auth token and the client secret are stored encrypted.
Disconnect deletes the auth token. Mappings, the client secret, received events and metrics stay in Jasper, and metrics stop updating.
Jasper keeps each webhook it receives, including rejected ones, with its headers and sender IP address.
To stop the webhooks, remove the internal integration in Sentry.

Not available yet

Resolving or ignoring Sentry issues from Jasper.
Showing links between Sentry issues and pull requests.
Creating ClickUp tasks from Sentry issues.
Passing Sentry alerts on to email or chat.