Linking Dialpad 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.

Learn more

The Dialpad connector syncs your communication data – calls, users, call centers, departments, offices, contacts, numbers, rooms, channels, coaching teams, and call labels – into PostHog, so you can analyze your call activity alongside your product data.

Prerequisites

You need:

A Dialpad account with company admin access.
A company-level API key. User-level keys are rejected because they only import one user's data. A company admin can create the key in Dialpad under Admin Center → Authentication → API keys.
To import the calls table, the API key needs the calls:list scope.

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 Dialpad, you'll need:

API key – a company admin API key from your Dialpad account. Create one under Admin Center → Authentication → API keys. Use a company API key so the import includes your whole company.

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.

The calls table supports incremental sync using the date_started field. Each sync starts with a 3-hour lookback window because Dialpad only lists a call after it ends – this ensures recently completed calls aren't missed. Duplicate rows are deduplicated automatically by call_id.

All other tables use full refresh sync.

Configuration

Option	Type	Required
`API key`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`calls`	A call that has ended, with its participants, timing, recordings and call center details.	Incremental, Full refresh	date_started	—
`call_centers`	A call center: a group of operators that answers calls to shared numbers, with its routing and hours.	Full refresh	—	—
`call_labels`	A call label that the company defined. Users tag calls with labels, for example to mark the call outcome.	Full refresh	—	—
`channels`	A Dialpad messaging channel in the company.	Full refresh	—	—
`coaching_teams`	A coaching team, where coaches listen to and train trainee agents.	Full refresh	—	—
`contacts`	A shared company contact, or a contact local to one user.	Full refresh	—	—
`departments`	A department: a group of users that answers calls to shared numbers, with its routing and hours.	Full refresh	—	—
`numbers`	A phone number in the company and the user, room or group it is assigned to.	Full refresh	—	—
`offices`	An office: a location in the company with its own main line, hours and routing.	Full refresh	—	—
`rooms`	A room: a shared phone, such as a conference room or lobby phone, that is not assigned to a person.	Full refresh	—	—
`users`	A user in the Dialpad company, with every user state (active, suspended, cancelled, deleted and pending).	Full refresh	—	—

Troubleshooting

"Your API key can't read your whole Dialpad company"

You're using a user-level API key instead of a company-level key. Create a company admin API key in Dialpad under Admin Center → Authentication → API keys.

"Your API key can't read this table"

Some tables require specific permissions. The calls table needs an API key with the calls:list scope. The numbers table needs a company admin API key. The table picker marks tables your key can't access.

"Dialpad rejected this API key"

Your API key is invalid or has been revoked. Create a new key in Dialpad under Admin Center → Authentication → API keys, then update the source in PostHog.

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.