Linking Bland AI as a source
This source is currently in alpha. The interface and available tables may change.
The Bland AI connector syncs your AI phone call data – calls, per-call transcripts, and conversational pathways – into the PostHog Data warehouse, so you can analyze your voice agents' performance alongside your product data.
Prerequisites
You need a Bland AI account with access to an API key. The key grants read access to all calls, transcripts, and pathways in your account.
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 Bland AI, you'll need:
- API key – find it in the Bland 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 call_transcripts table fetches each call's transcript individually (Bland excludes transcripts from its call list API for size reasons), so it makes one extra API request per call and is disabled by default. Enable it only if you need utterance-level transcript data.
Incremental syncs on the call tables track the call creation time. Post-call analysis added to older calls after a sync won't be picked up incrementally – run a full refresh if you need to re-sync updated analysis fields.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
calls | Metadata for every call dispatched or received by your account: status, timing, cost, post-call analysis, and pathway info. Transcripts are excluded — sync call_transcripts for those. | Incremental, Full refresh | created_at | — |
call_transcripts | One row per utterance spoken during a call. Requires one extra API request per call (transcripts are excluded from the call list endpoint), so syncs are slower than the calls table. | Incremental, Full refresh | call_created_at | — |
pathways | Your conversational pathways — the node/edge graphs that drive agent conversations. Full refresh only (the API has no timestamp filters for pathways). | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key is invalid or has been revoked. Create a new key in the Bland dashboard, 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.