Linking Courier as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Courier connector syncs your notification data – messages, audit events, audiences, brands, and tenants – into PostHog, so you can analyze notification delivery and engagement alongside your product data.
Prerequisites
You need a Courier account with access to an API key. Find your API key in the Courier dashboard under Settings > API Keys. Either the Live or Test key works – the key determines which environment's data is synced.
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.
You need your Courier API key. Find it in the Courier dashboard under Settings > API Keys.
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_attimestamp). 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.
The Messages table supports incremental sync on enqueued using Courier's server-side enqueued_after filter, so ongoing syncs only fetch new messages. Engagement fields that change on existing messages after delivery (like clicked, opened, and delivered) are only refreshed by a full refresh, so consider scheduling periodic full refreshes of Messages if you rely on those fields.
The AuditEvents, Audiences, Brands, and Tenants tables don't have server-side timestamp filters in Courier's API, so they always sync as a full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Messages | A message you've sent through Courier, with its current delivery status and engagement timestamps. | Incremental, Full refresh | enqueued | — |
AuditEvents | An account-level activity log entry recording an action taken by a user or API key in your Courier workspace. | Full refresh | — | — |
Audiences | A saved, filter-defined segment of recipients used to target notifications. | Full refresh | — | — |
Brands | A branding profile (colors, logo, templates) that can be applied to messages sent through Courier. | Full refresh | — | — |
Tenants | A tenant used to scope notification sending and preferences for a group of recipients (e.g. a customer account). | Full refresh | — | — |
Troubleshooting
If the source fails to connect or a sync stops with an authorization error, your API key is likely invalid or revoked – generate a new key in the Courier dashboard under Settings > API Keys and update the source credentials. If a table is unexpectedly empty, check that you connected the key for the right Courier environment, since each key only sees its own environment's data.
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.