> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Sentry as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/sentry

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Creating a Sentry Auth Token](#creating-a-sentry-auth-token)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Available datasets and endpoints](#available-datasets-and-endpoints)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Sentry connector can link data from your Sentry organization into PostHog.

## Creating a Sentry Auth Token

Sentry supports several authentication methods, but for PostHog you should use an **Auth Token**.

1.  In Sentry, create a token from your account settings (for internal integrations or personal tokens).
2.  Give the token the following scopes to sync all datasets: `alerts:read`, `event:read`, `member:read`, `org:read`, `project:read`, `team:read`.
3.  Copy the token and paste it into PostHog when linking your source.

For token setup details, see Sentry's [Authentication docs](https://docs.sentry.io/api/auth/).

Once the syncs are complete, you can start using Sentry data in PostHog.

To link Sentry:

1.  Go to the [Data pipeline sources page](https://app.posthog.com/data-management/sources) in PostHog.
2.  Click **\+ New source** and then click **Link** next to Sentry.
3.  In Sentry, create an **Auth Token** and copy it. PostHog currently supports Auth Tokens only.
4.  In PostHog, enter your Sentry **Organization slug** and **Auth Token**.
5.  Click **Next**, choose the tables you want to sync, and then click **Import**.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Auth token` | password | Yes |
| `Organization slug` | text | Yes |
| `API base URL` | select | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | A Sentry project that error and performance events are reported to. | Full refresh | — | — |
| `teams` | A team within the Sentry organization that owns projects. | Full refresh | — | — |
| `members` | A member of the Sentry organization. | Full refresh | — | — |
| `releases` | A release tracked in Sentry, used to associate errors with deployed code versions. | Full refresh | — | — |
| `environments` | An environment (e.g. production, staging) that events are tagged with. | Full refresh | — | — |
| `monitors` | A cron monitor that tracks the health of scheduled jobs. | Full refresh | — | — |
| `issues` | A group of similar error events aggregated into a single issue. | Incremental, Full refresh | lastSeen, firstSeen | — |
| `project_events` | Individual error events captured for a project. | Incremental, Full refresh | dateReceived | — |
| `project_users` | Users seen in events for a project. | Full refresh | — | — |
| `project_client_keys` | Client (DSN) keys that authenticate event submission to a project. | Full refresh | — | — |
| `project_service_hooks` | Service hooks that send a project's events to external services. | Full refresh | — | — |
| `issue_events` | Individual error events belonging to a specific issue. | Incremental, Full refresh | dateReceived | — |
| `issue_hashes` | Grouping hashes that determine which events are bucketed into an issue. | Full refresh | — | — |
| `issue_tag_values` | The distinct values of a tag observed across an issue's events, with counts. | Incremental, Full refresh | lastSeen | — |
| `repos` | A version control repository linked to the Sentry organization. | Full refresh | — | — |
| `dashboards` | A custom dashboard defined in the organization. | Full refresh | — | — |
| `discover_saved_queries` | A saved Discover query in the organization. | Full refresh | — | — |
| `workflows` | An alert workflow that reacts to detector activity in the organization. | Full refresh | — | — |
| `detectors` | A detector that watches a data source and opens issues when its conditions are met. | Full refresh | — | — |
| `organization_tags` | A tag key seen across the organization's events, with value cardinality. | Full refresh | — | — |
| `integrations` | A third-party integration installed on the organization. | Full refresh | — | — |
| `sentry_app_installations` | An integration platform app installed on the organization. | Full refresh | — | — |
| `replays` | Metadata for a session replay recorded in the organization. | Incremental, Full refresh | started\_at | — |
| `organization_events` | Error events across the organization, queried through Discover. | Incremental, Full refresh | timestamp | — |
| `sessions` | Release health session counts per day, grouped by project, release, environment, and session status. | Incremental, Full refresh | interval\_start | — |
| `organization_stats` | Daily event volume for the organization, grouped by outcome, data category, and drop reason. | Incremental, Full refresh | interval\_start | — |
| `organization_stats_summary` | Event volume by project and data category over the retention window. | Full refresh | — | — |
| `trace_item_attributes` | The attribute keys available on each trace item dataset (spans, logs, trace metrics). | Full refresh | — | — |
| `trace_item_stats` | Attribute value distributions computed over recent trace items. | Full refresh | — | — |
| `project_ownership` | The issue-owner rules configured on a project. | Full refresh | — | — |
| `project_stats` | Daily event counts per project, one row per statistic per day. | Incremental, Full refresh | timestamp | — |
| `release_deploys` | A deploy recorded against a release. | Full refresh | — | — |
| `release_commits` | A commit associated with a release. | Full refresh | — | — |
| `repo_commits` | Commits Sentry has ingested for a linked repository. | Full refresh | — | — |
| `monitor_checkins` | A check-in reported by a cron monitor. | Full refresh | — | — |
| `project_user_feedback` | A user report submitted against an error in a project. | Full refresh | — | — |
| `project_filters` | An inbound data filter configured on a project. | Full refresh | — | — |

## Available datasets and endpoints

The Sentry source currently supports syncing the following datasets and API endpoints:

| Dataset | Endpoint path |
| --- | --- |
| `projects` | `/organizations/{organization_slug}/projects/` |
| `teams` | `/organizations/{organization_slug}/teams/` |
| `members` | `/organizations/{organization_slug}/members/` |
| `releases` | `/organizations/{organization_slug}/releases/` |
| `environments` | `/organizations/{organization_slug}/environments/` |
| `monitors` | `/organizations/{organization_slug}/monitors/` |
| `issues` | `/organizations/{organization_slug}/issues/` |
| `project_events` | `/projects/{organization_slug}/{project_slug}/events/` |
| `project_users` | `/projects/{organization_slug}/{project_slug}/users/` |
| `project_client_keys` | `/projects/{organization_slug}/{project_slug}/keys/` |
| `project_service_hooks` | `/projects/{organization_slug}/{project_slug}/hooks/` |
| `issue_events` | `/issues/{issue_id}/events/` |
| `issue_hashes` | `/issues/{issue_id}/hashes/` |
| `issue_tag_values` | `/issues/{issue_id}/tags/{key}/values/` |