Integrations / HCP Terraform
HCP Terraform
HCP Terraform and Terraform Enterprise for organizations, projects, workspaces, runs, state versions, and policy evidence.
API key
Indexes
Actions
Events
What Telara does
Capability matrix
Before you connect
Prerequisites
An HCP Terraform (Terraform Cloud) organization.
Permission to create a user, team, or organization token.
Vendor setup
Get the credential
1
Create a token
In HCP Terraform, open User settings → Tokens (or Organization settings → API tokens). Create a token named for Telara.
2
Paste in Telara
Settings → Integrations → HCP Terraform.
In Telara
Connect in Telara
API key
HCP Terraform user, team, or organization token.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Organization | Partial — not every record the vendor holds is synced |
| Iac workspace | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Organization | Up to 1 hour | Removed records disappear on the next full sync |
| Iac workspace | Up to 1 hour | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Organization, Iac workspace.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
A token scoped to one org will not list another.
TFE vs HCP host mismatch looks like a bad token.