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

# Linking Airbrake as a source

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

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

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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 Airbrake connector syncs your error monitoring data – projects, error groups, error occurrences (notices), and deploys – into PostHog, so you can track error rates by project and environment over time and correlate error spikes with deploys.

## Prerequisites

You need an Airbrake account with a **user API key**. Every project your user can access is synced.

## 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.

You need your Airbrake user API key. Find it in your Airbrake **User settings** (your profile menu in the Airbrake dashboard). Per-project keys in Airbrake only allow error submission and won't work for syncing data.

## 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The `groups` table supports incremental sync on `createdAt`, which only picks up newly created error groups. Fields that change on existing groups (like `noticeCount`, `resolved`, and `lastNoticeAt`) are only refreshed by a full refresh, so consider scheduling periodic full refreshes if you rely on those fields.

The `notices` table fetches occurrences per error group across every project, making it the most API-expensive table. It is not synced by default and only the most recent pages of history are pulled per group.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `User API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | Airbrake projects accessible to the connected user key, with per-project error and deploy counters. | Full refresh | — | — |
| `groups` | Incremental syncs only pick up newly created error groups; fields that mutate on existing groups (noticeCount, resolved, lastNoticeAt) are only refreshed by a full refresh | Incremental, Full refresh | createdAt | — |
| `deploys` | Deploys tracked per project. Airbrake's API returns no deploy identifier, so this table is full-refresh only; projectId is added by PostHog for joinability. | Full refresh | — | — |
| `notices` | Individual error occurrences, fetched per error group across every project — the most API-expensive table, capped at the most recent pages per group | Full refresh | — | — |

Deploy rows don't include a project reference in Airbrake's API, so PostHog adds a `projectId` column to the `deploys` table for joining against `projects`.

## Troubleshooting

If the source fails to connect or a sync stops with an authorization error, your user API key is likely invalid or revoked – generate a new key in your Airbrake user settings and update the source credentials.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/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.