# Linking Bugsnag as a source - Docs

![](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`

[Learn more](/wizard.md)

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

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The BugSnag connector pulls your error-monitoring data into the PostHog Data warehouse, so you can analyze your errors, events, and releases alongside your product data.

## Prerequisites

You need a BugSnag account so you can generate a personal auth token. The token inherits your account's access, so it can read every organization and project you can see.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Bugsnag, you'll need:

-   **Auth token** – generate a personal auth token in the **My Account** section of your [BugSnag account settings](https://app.bugsnag.com/settings/my-account/).

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

This source is full refresh only.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Auth token | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| organizations | An organization the auth token can access; the top of BugSnag's resource hierarchy, owning projects and collaborators. | Full refresh | — | — |
| projects | An application or service monitored in BugSnag. Errors and events are scoped to a project. | Full refresh | — | — |
| collaborators | A user with access to an organization in BugSnag. | Full refresh | — | — |
| teams | A team within an organization, used to group collaborators and scope project access. | Full refresh | — | — |
| errors | A group of similar events (a distinct error) in a project, with aggregate counts and first/last-seen timestamps. | Full refresh | — | — |
| events | One row per captured event. Can be very large — full refresh only, off by default. | Full refresh | — | — |
| releases | A released version of a project's app, with stability and event metrics. | Full refresh | — | — |
| pivots | — | Full refresh | — | — |
| event_fields | — | Full refresh | — | — |
| trace_fields | — | Full refresh | — | — |
| saved_searches | A saved error filter/search defined in a project. | Full refresh | — | — |

## Troubleshooting

-   If you see an authentication error, your BugSnag auth token may be invalid or revoked. Generate a new personal auth token in your BugSnag account settings, then reconnect.
-   If you see a permission error, the token does not have access to the requested data. Check the token's account permissions, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better