Linking Humanitec 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 Humanitec connector syncs applications, environments, deployments, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Humanitec API token and organization ID to pull your Humanitec data.
Create a service user token in your Humanitec organization. In Humanitec, open Service users, select a user, then select Add new API token. The service user needs read access to the applications and environments you want to sync.
This source connects to the Platform Orchestrator API at api.humanitec.io.
You'll be asked for:
API token: A service user token from your Humanitec organization.
Organization ID: Your Humanitec organization identifier (lowercase letters, numbers, and single hyphens).
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 Humanitec tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Organization ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
applications | Applications group workloads that deploy together into an environment. | Full refresh | — | — |
environments | Environments provide independent spaces where applications run. | Full refresh | — | — |
deployments | Deployments record changes to the running state of an environment. | Full refresh | — | — |
active_resources | Active resources are infrastructure resources provisioned for an environment. | Full refresh | — | — |
environment_types | Environment types group environments for management and resource selection. | Full refresh | — | — |
pipelines | Pipelines define automated deployment workflows within an application. | Full refresh | — | — |
Troubleshooting
If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
If the token cannot read a resource, check that the service user has the correct roles in your organization.
If the organization is not found, verify the organization ID and ensure the service user has access to it.
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.