Linking CallRail as a source
This source is currently in alpha. The interface and available tables may change.
The CallRail connector syncs your call-tracking data into the PostHog Data warehouse, so you can analyze your calls and attribution alongside your product data.
Prerequisites
You need a CallRail account with API access so you can create an API key. API keys are scoped to the creating user, so the key only sees data that user can access.
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 CallRail, you'll need:
- API key – create one under Account settings → Integrations → API Keys in CallRail.
- Account ID – optional. Leave it blank to use the first account your key can access, or set it to sync a specific account.
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.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Account ID | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
calls | Tracked phone calls captured by CallRail, including caller details, attribution source, and outcome. | Incremental, Full refresh | start_time | — |
companies | Companies configured in the CallRail account. A company groups trackers, calls, and form submissions. | Full refresh | — | — |
form_submissions | Form submissions captured by CallRail Form Tracking, with attribution to the originating marketing source. | Incremental, Full refresh | submitted_at | — |
text_messages | SMS conversations between callers and the business, captured by CallRail. | Full refresh | — | — |
trackers | Tracking phone numbers and form trackers used to attribute calls and submissions to marketing sources. | Full refresh | — | — |
users | Users with access to the CallRail account. | Full refresh | — | — |
tags | Tags available in the CallRail account for categorizing calls and conversations. | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your CallRail API key is invalid or has been revoked. Create a new key under Account settings → Integrations → API Keys, then reconnect.
- If you get a permission error, your API key does not have access to this data. The key only sees what its creating user can access, so check the user's permissions, 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.