Linking ChartHop as a source
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.
This source is currently in alpha. The interface and available tables may change.
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
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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_attimestamp). 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 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 | — | — |
Troubleshooting
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.