> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking babelforce as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/babelforce

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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](https://help.babelforce.com/hc/en-us/articles/6418329977108-Authentication-Best-Practice) 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_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](https://posthog.com/docs/data-pipelines/sources.md#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 | — | — |
| `conversation_events` | Timeline of everything that happened in a conversation: the calls, messages, queue and application steps it passed through. | Full refresh | — | — |
| `event_definitions` | Catalog of the event types available on the account, including custom ones, used to trigger automations. Not a stream of events that happened - see conversation\_events for that. | Full refresh | — | — |
| `outbound_campaigns` | Outbound dialer campaigns and their dialing configuration. | Full refresh | — | — |
| `outbound_campaign_statistics` | Per-agent time breakdown for an outbound campaign. | Full refresh | — | — |
| `outbound_lists` | Lead lists the outbound dialer works through. | Full refresh | — | — |
| `outbound_leads` | The leads on an outbound dialer list, with their dialing outcome so far. | 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.