Linking Doppler as a source
This source is currently in alpha. The interface and available tables may change.
The Doppler connector syncs your secrets management metadata into the PostHog Data warehouse: projects, environments, configs, workplace members, and the activity log of config and access changes. This is useful for audit, change tracking, and compliance reporting. Secret values are never synced.
Prerequisites
You need a Doppler API token with read access to your workplace and the projects you want to sync. A personal token or a service account token both work. Service tokens scoped to a single config are too narrow for this connector.
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 Doppler, you'll need:
- API token – create a personal token under Settings → API in your Doppler dashboard, or create a service account with read access and generate a token for it.
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 activity log is append-only, so incremental sync is recommended for the activity_logs table: each sync only fetches entries newer than the last synced one. The remaining tables are small and only support full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | A Doppler project, the top-level grouping of environments and configs for an application or service. | Full refresh | — | — |
environments | An environment within a Doppler project (e.g. development, staging, production). | Full refresh | — | — |
configs | A config within a Doppler project environment, holding a set of secrets. Secret values are not synced. | Full refresh | — | — |
activity_logs | Workplace activity log of project, config, and access changes. Incremental syncs stop paging once they reach already-synced entries. | Incremental, Full refresh | created_at | — |
workplace_users | Users belonging to the Doppler workplace, with their workplace-level access role. | Full refresh | — | — |
groups | User groups in the Doppler workplace, used to manage project access in bulk. | Full refresh | — | — |
service_accounts | Machine identities in the Doppler workplace used for programmatic access. | Full refresh | — | — |
invites | Pending invitations to join the Doppler workplace. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API token is invalid or has been revoked. Create a new token in your Doppler dashboard, then reconnect.
- If you see a permissions error, the token is missing read access to your workplace or one of its projects. Check the token's access, then reconnect.
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.