Linking babelforce as a source
This source is currently in alpha. The interface and available tables may change.
The babelforce connector syncs your contact center data – call reporting, agents, agent groups, queues, service numbers, recordings, SMS messages, and conversations – into PostHog.
Prerequisites
You need a babelforce account with a user that has manager rights, so you can create API credentials in the manager app.
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.
To connect babelforce, you need:
- Environment (subdomain): the subdomain your babelforce account is served from. This is usually
services, unless you are on a dedicated environment with a custom subdomain (check the URL you use to open the manager app). - Access ID and Access token: an API credential pair created in your babelforce manager app. See babelforce's authentication guide for how to create one.
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 calls table supports incremental syncs using the call's dateCreated timestamp. All other tables are reference data and use full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Environment (subdomain) | text | Yes |
Access ID | text | Yes |
Access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
calls | Call reporting records for every inbound and outbound call leg, including timing, state, and finish reason. | Incremental, Full refresh | dateCreated | — |
agents | Contact center agents, including their line state, presence, and group membership. | Full refresh | — | — |
agent_groups | Groups used to organize agents for routing and reporting. | Full refresh | — | — |
queues | Call queues with their dialing and wrap-up configuration. | Full refresh | — | — |
numbers | Service phone numbers configured on the account. | Full refresh | — | — |
recordings | Call recordings and their storage state. | Full refresh | — | — |
sms | Inbound and outbound SMS messages. | Full refresh | — | — |
conversations | Conversations grouping the calls and messages exchanged with a single phone number. | Full refresh | — | — |
Troubleshooting
If the connection fails with an authentication error, check that the environment subdomain matches your account and that the access ID and access token belong to a user with manager rights.
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.