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

# Linking Planhat as a source

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

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

![](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 Planhat connector syncs your customer success data – companies, end users, users, licenses, assets, and NPS responses – into the PostHog Data warehouse, so you can analyze your customer success metrics alongside your product data.

## Prerequisites

You need a Planhat account with permission to create a Private App under **Settings → Service Accounts**.

## 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.

When linking Planhat, you'll need:

-   **API access token** – create a Private App in [Planhat](https://app.planhat.com) under **Settings → Service Accounts**. The token is shown once, so copy it immediately.

## 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.

All Planhat tables use full refresh sync mode.

## Configuration

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

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `companies` | A customer account (company) tracked in Planhat, the core object health scores and revenue attach to. | Full refresh | — | — |
| `endusers` | A contact (end user) at one of your customer companies. | Full refresh | — | — |
| `users` | A Planhat team member (internal user) in your workspace. | Full refresh | — | — |
| `licenses` | A license or subscription line item attached to a company, driving recurring revenue. | Full refresh | — | — |
| `assets` | An asset (a sub-unit of a company such as a product instance, project, or store) tracked in Planhat. | Full refresh | — | — |
| `nps` | An NPS survey response collected from an end user. | Full refresh | — | — |
| `conversations` | A customer conversation in Planhat, such as an email, chat, call, ticket or logged note. | Full refresh | — | — |
| `tickets` | A support ticket tied to a customer company, usually synced from a helpdesk such as Zendesk. | Full refresh | — | — |
| `invoices` | An invoice record for a customer company, usually generated when a license is created or renewed. | Full refresh | — | — |
| `sales` | A non-recurring revenue (NRR) sale, such as an onboarding fee or a one-off services project. | Full refresh | — | — |

## Troubleshooting

-   If you see an authentication error, your API access token is invalid or has been revoked. Generate a new token from a Private App under **Settings → Service Accounts** in Planhat, then reconnect.
-   If you see a permissions error, the token does not have access to this data. Check the Private App's scopes in your Planhat account, then reconnect.

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.