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

# Linking ChartHop as a source

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

> **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 ChartHop connector syncs your people analytics data – people, jobs, org groups, compensation and org changes, and time off – into PostHog, so you can analyze headcount, org structure, and workforce changes alongside your product data.

## Prerequisites

You need a ChartHop account with permission to create an API token. The token's access level determines which data the source can read.

## 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 ChartHop, you'll need:

-   **API token** – generate one in ChartHop under **Settings → API**.
-   **Organization ID or slug** (optional) – only needed if your token can access more than one organization. When the token is scoped to a single organization, PostHog detects it automatically.

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

Most ChartHop tables are synced with full refresh, since the API doesn't expose an updated-since filter for them. The `changes` table supports incremental sync on the change's effective `date`.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |
| `Organization ID or slug (optional)` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `persons` | People in the organization, including ex-employees, one row per person. | Full refresh | — | — |
| `jobs` | Jobs (filled and open positions) in the organization, one row per job. | Full refresh | — | — |
| `groups` | Groups in the organization, such as departments and teams, one row per group. | Full refresh | — | — |
| `group_types` | Group types configured for the organization (e.g. department, team, location). | Full refresh | — | — |
| `job_levels` | Job levels configured for the organization's leveling framework. | Full refresh | — | — |
| `job_codes` | Job codes mapping codes to standardized job titles. | Full refresh | — | — |
| `changes` | Changes across the organization — hires, departures, moves, and field updates including compensation changes. | Incremental, Full refresh | date | — |
| `time_off` | Time off requests for people in the organization. | Full refresh | — | — |
| `time_off_policies` | Time off policies configured for the organization, one row per policy. Resolves the policy ids carried on time\_off rows. | Full refresh | — | — |
| `comp_bands` | Compensation bands configured for the organization, one row per band. Resolves the band a job or job level sits in. | Full refresh | — | — |
| `compensation_history` | Enriched compensation change history, one row per comp change, with the person, job, and pay values as of the change date. | Full refresh | — | — |

## Troubleshooting

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.