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

# Linking Kustomer as a source

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

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

Enter your Kustomer credentials to pull your customer service data – customers, conversations, companies, users, teams, tags, brands, sub-statuses, and satisfaction forms – 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 Kustomer.

3.  Next, gather your Kustomer credentials:

    -   **Organization name** – the subdomain from your Kustomer URL, e.g. `myorg` for `myorg.kustomerapp.com`. You can also paste the full URL and PostHog will extract the subdomain automatically.
    -   **API key** – create one in Kustomer under **Settings → Security → API Keys**. Grant read roles for the data you want to sync (e.g. `org.user.read`).

    This source authenticates with a Bearer token (API key) and requires read access to the endpoints you want to sync.

4.  Back in PostHog, enter the credentials 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 Kustomer data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `customers` | Customers | Full refresh |
| `conversations` | Conversations | Full refresh |
| `companies` | Companies (business accounts) that customers belong to | Full refresh |
| `users` | Helpdesk users (agents) | Full refresh |
| `teams` | Teams | Full refresh |
| `tags` | Tags | Full refresh |
| `brands` | Brands | Full refresh |
| `sub_statuses` | Conversation sub-statuses (finer-grained status states) | Full refresh |
| `satisfaction_forms` | CSAT survey form definitions | Full refresh |

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

## Sync limitations

All Kustomer tables are full refresh only. Kustomer's GET list endpoints have no server-side timestamp filter, so true incremental sync is not currently possible.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Organization name` | text | Yes |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `customers` | A person or company that interacts with your business — the central record in Kustomer. | Full refresh | — | — |
| `conversations` | A thread of messages and activity between a customer and your support team. | Full refresh | — | — |
| `users` | A member of your Kustomer organization (an agent, admin, or other team member). | Full refresh | — | — |
| `teams` | A group of users in Kustomer used for routing and assignment. | Full refresh | — | — |
| `tags` | A label that can be applied to customers, conversations, or messages to categorize them. | Full refresh | — | — |
| `brands` | A brand identity in Kustomer, used to support multiple products or businesses from one org. | Full refresh | — | — |
| `companies` | A company (business account) that customers can be associated with, used for account-level reporting. | Full refresh | — | — |
| `sub_statuses` | A conversation sub-status, a finer-grained state nested under a conversation status. | Full refresh | — | — |
| `satisfaction_forms` | A satisfaction (CSAT) survey form, defining when and how customers are asked to rate a conversation. | Full refresh | — | — |
| `messages` | A single message sent or received in a conversation, on any channel. | Full refresh | — | — |
| `notes` | An internal note that an agent added to a conversation or customer. Customers do not see notes. | Full refresh | — | — |
| `queues` | A routing queue that holds conversations and other work until an agent is assigned. | Full refresh | — | — |
| `work_items` | A unit of routed work, such as a conversation, that a queue assigns to an agent. | Full refresh | — | — |
| `work_sessions` | An agent's routing session, from sign-in to sign-out, with capacity and time spent in each status. | Full refresh | — | — |