Linking HashiCorp (HCP Terraform / Terraform Cloud) 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 HashiCorp (HCP Terraform / Terraform Cloud) 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.
Sync organizations, projects, teams, workspaces, runs, and state versions from HCP Terraform (formerly Terraform Cloud) to analyze infrastructure change frequency, plan/apply durations, and failure rates.
Create an API token in your HCP Terraform organization settings under API tokens - an organization token is recommended so every workspace is visible. Team and user tokens also work but only see the workspaces they have access to.
Only the SaaS API at app.terraform.io is supported; self-hosted Terraform Enterprise is not currently supported.
You'll be asked for:
- API token
- Organization name: for example
my-organization.
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 HashiCorp (HCP Terraform / Terraform Cloud) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Organization name | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organizations | The configured HCP Terraform organization. An organization is a shared space for teams to collaborate on workspaces. | Full refresh | — | — |
projects | Projects in the configured organization. Projects group related workspaces and let teams organize permissions at a higher level. | Full refresh | — | — |
teams | Teams in the configured organization. Teams group users and are granted permissions on workspaces and projects. | Full refresh | — | — |
workspaces | Workspaces in the configured organization. A workspace holds a Terraform configuration, its state, and its run history. | Full refresh | — | — |
runs | Runs across every workspace in the organization. A run is one plan/apply cycle performed against a workspace's configuration. | Incremental, Full refresh | created_at | — |
state_versions | State versions across every workspace in the organization. A state version is one snapshot of a workspace's Terraform state, created by an apply or an upload. | Incremental, Full refresh | created_at | — |
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 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.