Linking Deepgram 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 Deepgram connector syncs projects, members, keys, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Deepgram API key to sync your Deepgram Management API data.
You can create an API key in your Deepgram Console under Settings → API Keys. A key with a read-capable scope (e.g. member) is sufficient - the source only reads projects, members, keys, balances, invites, and the request log.
You'll be asked for:
- API key
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.
Some Deepgram tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | A Deepgram project — the top-level container that owns members, API keys, balances, and requests. | Full refresh | — | project_id |
members | A user who is a member of the project, with their assigned scopes. | Full refresh | — | project_id, member_id |
keys | An API key belonging to the project. The nested key object is flattened onto the row root, alongside the member the key was created for. | Full refresh | — | project_id, api_key_id |
balances | A funding balance for the project, in the account's billing units. | Full refresh | — | project_id, balance_id |
invites | A pending invitation for a user to join the project. | Full refresh | — | project_id, email |
requests | A single inference request made against the project, with model/feature metadata, the response code, and the time it was created. Synced incrementally on | Incremental, Full refresh | created | project_id, request_id |
models | A model the project can call, public or non-public, with the identifier that request rows refer to. Speech-to-text and text-to-speech models share the table and are told apart by | Full refresh | — | project_id, uuid |
usage_breakdown | Usage totals for one period of a project, broken down by the dimensions the request grouped on. Synced incrementally on the period's start date. | Incremental, Full refresh | start | project_id, start, end, grouping_key |
billing_breakdown | What a project was billed for one period, broken down by the dimensions the request grouped on. Synced incrementally on the period's start date. | Incremental, Full refresh | start | project_id, start, end, grouping_key |
usage_fields | The models, tags, processing methods and features the project used in the period. These are the dimensions a usage breakdown can be sliced by. One row per value. | Full refresh | — | project_id, field, value |
billing_fields | The accessors, deployments, tags and line items the project was billed on in the period. These are the dimensions a billing breakdown can be sliced by. One row per value. | Full refresh | — | project_id, field, value |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.