Linking Hex as a source
This source is currently in alpha. The interface and available tables may change.
The Hex connector syncs your Hex workspace data into the PostHog Data warehouse, so you can analyze your projects, scheduled notebook runs, users, groups, and collections alongside your product data. It's especially useful for monitoring the reliability, duration, and error rates of scheduled Hex project runs.
Prerequisites
You need a Hex account with access to the Hex API so you can create an API token. A personal token inherits your permissions; workspace tokens are available on some Hex plans and can read across the whole workspace.
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 Hex, you'll need:
- API token – create one in Hex under Workspace settings → API keys.
- Workspace URL – only needed for single-tenant or self-hosted Hex deployments (for example
https://acme.hex.tech). Leave it empty if your workspace is on Hex's multi-tenant cloud atapp.hex.tech.
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.
All Hex tables are full refresh only, since the Hex API exposes no incremental sync filter.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Workspace URL (single-tenant only) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | A Hex project (notebook or app) in the workspace, including ownership, status, categories, usage analytics, and schedule metadata. | Full refresh | — | — |
project_runs | An execution of a published Hex project triggered via the API, a schedule, or an app refresh, with its status and timing. | Full refresh | — | — |
users | A member of the Hex workspace with their role and last login time. | Full refresh | — | — |
groups | A permission group in the Hex workspace, used to manage access to projects and collections. | Full refresh | — | — |
collections | A collection in the Hex workspace, used to organize and share sets of projects. | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your API token is invalid or was revoked. Create a new token under Workspace settings → API keys in Hex, then reconnect.
- If you get a permission error, your token can't read this data. Personal tokens only see what your Hex user can see, so use a token from a user with broader access (or a workspace token), then reconnect.
- The
project_runstable only contains runs of published projects triggered via the API, a schedule, or an app refresh. Runs from editing a project in the notebook view don't appear in Hex's API.
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.