Linking Honeybadger as a source

Alpha release

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

The Honeybadger connector syncs your error monitoring data – projects, errors (faults), error occurrences (notices), deployments, and uptime checks – into PostHog, so you can track error rates across environments and correlate error spikes with releases.

Prerequisites

You need a Honeybadger account and your personal authentication token, available on your Honeybadger profile page. The token grants read access to every project your Honeybadger user can see.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
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 Honeybadger, you'll need:

Personal authentication token – found on your Honeybadger profile page under Authentication token.

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 for a full explanation of how each mode works and how to choose between them.

We recommend incremental sync for the faults, notices, and deploys tables. Honeybadger's API allows 360 requests per hour with at most 25 rows per page, so full refreshes of large accounts are slow – incremental syncs only fetch what changed since the last run.

The notices table is disabled by default because it is fetched one fault at a time, which can use up the API quota quickly on accounts with many errors. Enable it if you need per-occurrence detail such as request context and backtraces.

Configuration

Option	Type	Required
`Personal authentication token`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`projects`	A container that holds all your Honeybadger data for a single app or service.	Full refresh	—	—
`faults`	An error ('fault') grouping many individual occurrences (notices). Called an error in the Honeybadger UI.	Incremental, Full refresh	created_at, last_notice_at	—
`notices`	One row per error occurrence. Fetched per fault, so syncing large accounts is slow against Honeybadger's 360 requests/hour limit — prefer incremental sync	Incremental, Full refresh	created_at	—
`deploys`	A deployment recorded for a project, used to correlate errors with releases.	Incremental, Full refresh	created_at	—
`sites`	An uptime check ('site') configured for a project.	Full refresh	—	—

Troubleshooting

If a sync fails with an access denied error, your authentication token is invalid or was revoked – copy a fresh token from your Honeybadger profile page and update the source credentials.

Syncs that hit Honeybadger's 360 requests/hour rate limit pause and retry automatically, so a large initial backfill can take several hours to complete.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.