---
title: "Connect Sentry to Rig — Rig guide"
description: "Connect Sentry to Rig with a personal auth token and your organisation slug, and sync projects, issues, releases and members to your warehouse."
canonical: "https://rig.so/guides/connect-sentry"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Sentry to Rig

Rig syncs your Sentry projects, issues, releases and organisation members into your warehouse, so reliability questions can sit next to deploy and customer data. You connect with a personal auth token and your organisation slug.

## Before you start

- You need a Sentry account that can see the projects you want synced. A personal token reads what its owner can read.
- Find your organisation slug in your Sentry address, which looks like `sentry.io/organizations/<slug>/`.

## Step 1: Create a Sentry personal auth token

1. In Sentry, open the account dropdown at the top left and choose **Personal Tokens**.
2. Create a new token and tick the scopes `org:read`, `project:read` and `event:read`.
3. Copy the token. Sentry does not let you edit a personal token's scopes later, so create a new one if you need to change them.

Use a personal token
Sentry's organisation tokens have fixed permissions aimed at CI tasks, so create a personal token where you choose the scopes yourself.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Sentry**, open the card and click `Connect`.
3. **Sentry auth token**: The personal token you created.
4. **Organization slug**: The slug from your Sentry address.
5. **Host**: Leave it as it is for Sentry's cloud service. For a self-hosted Sentry enter its address.
6. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
7. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Sentry lands in its own `sentry` schema in your warehouse:

- **Projects**: Every project in the organisation.
- **Issues**: Grouped errors with their status, counts and timestamps.
- **Releases**: Each release you have registered in Sentry.
- **Members**: The people in your organisation.

## Good to know

- Rig reads grouped issues, so counts come from the issue rows and individual error events are not synced.
- Releases only appear when your build process registers them with Sentry.
- A personal token inherits your own project access, so use an account that can see every project you want synced.
- To disconnect Sentry, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Track error frequency and incident trends
- Measure release health and regression rates
- Prioritise the bug backlog by user impact

[More ideas for using Sentry](https://rig.so/integrations/sentry)

## Sentry documentation

- [Sentry auth tokens](https://docs.sentry.io/account/auth-tokens/)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-sentry)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)