Linking env0 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 env0 connector syncs organizations, projects, teams, 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 env0 API key credentials to pull your env0 data.
You can create an organization API key in your env0 Organization Settings > API Keys, or a personal API key from your user settings. The key needs read access to the organizations you want to sync.
Environment cost data is only available for environments with cost monitoring configured.
You'll be asked for:
- API key ID
- API key secret
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 env0 tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key ID | text | Yes |
API key secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organizations | An env0 organization the API key can access, including its policies and plan settings. | Full refresh | — | — |
projects | A project groups environments, templates, and team access under an organization. | Full refresh | — | — |
teams | A team of users used to assign roles and project access within an organization. | Full refresh | — | — |
templates | A template (blueprint) defines a deployable environment type: its IaC repository, revision, and tooling. | Full refresh | — | — |
environments | An environment is a deployment managed by env0 — the live instance of a template within a project. | Full refresh | — | — |
deployments | A deployment log records one deploy, destroy, plan, or drift-detection run of an environment. | Incremental, Full refresh | startedAt | — |
environment_costs | Daily cloud cost records for an environment over the last year. Requires cost monitoring to be configured for the environment. | Full refresh | — | — |
project_costs | Daily cloud cost records for a project over the last year, rolling up the costs of the environments it contains. Requires cost monitoring to be configured. | Full refresh | — | — |
organization_costs | Daily cloud cost data points for an organization over the last year, one per date and project. Requires cost monitoring to be configured. | Full refresh | — | — |
organization_users | A user or API key with access to an organization, with the role it holds. Resolves the user ids stamped on deployments, environments, and role assignments. | Full refresh | — | — |
drift_causes | A drift cause detected across an organization: a change that made deployed infrastructure differ from the code, grouped across every environment it affects. | Full refresh | — | — |
deployment_resources | A resource that a deployment created or changed, giving one row per resource behind each deployment. | Incremental, Full refresh | deployment_started_at | — |
Troubleshooting
- If the connection fails with an authorization error, the API key ID is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.