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

# Linking Dixa as a source

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

> **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

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

**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

Sync your Dixa customer service data – conversations, agents, end users, queues, and tags – into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Dixa.
3.  Generate an API token in Dixa under **Settings > Integrations > API Tokens**. You need an admin-level token. The same token covers both the main API and the Exports API.
4.  Back in PostHog, paste the token in the **API token** field and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Dixa data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `conversations` | Customer conversations exported via the Dixa Exports API | Incremental |
| `agents` | Support agents | Full refresh |
| `endusers` | End users (customers) | Full refresh |
| `queues` | Queue configurations | Full refresh |
| `tags` | Tags used for organizing conversations | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

The `conversations` table uses the Dixa Exports API, which is rate limited to 10 requests per minute. Data is fetched in 30-day windows, so large historical backfills may take a while.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `conversations` | A customer service conversation from the Dixa Exports API, with timing and handling metrics. | Incremental, Full refresh | updated\_at | — |
| `conversation_messages` | A single message exchanged in a conversation, fetched per synced conversation. | Incremental, Full refresh | conversation\_updated\_at | — |
| `conversation_ratings` | A satisfaction survey response or offer for a conversation. A survey with several questions returns one row per question, all sharing the same rating id. | Incremental, Full refresh | conversation\_updated\_at | — |
| `conversation_activity_log` | A state change on a conversation — assignment, status change, transfer, tagging — across the whole organization. | Incremental, Full refresh | activityTimestamp | — |
| `agents` | An agent (team member) in the Dixa account. | Full refresh | — | — |
| `endusers` | An end user (customer) record in the Dixa account. | Full refresh | — | — |
| `queues` | A queue that conversations are routed into for handling by agents. | Full refresh | — | — |
| `tags` | A tag that can be applied to conversations to categorize them. | Full refresh | — | — |
| `teams` | A team that agents are grouped into. | Full refresh | — | — |
| `team_members` | Membership of an agent or admin in a team. One row per agent per team. | Full refresh | — | — |