Skip to main content
Telara

Integrations / PostHog

PostHog logo

PostHog

PostHog product engineering platform for analytics, feature flags, experiments, session replay, surveys, events, and release-impact investigation.

API key
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A PostHog organization (Cloud or self-hosted) Telara can reach.
Permission to create a personal API key.

Vendor setup

Get the credential

1
Create a personal API key
In PostHog, open your avatar → Personal API keys. Create a key that can read the project Telara should see.
2
Paste in Telara
Settings → Integrations → PostHog. Paste the key and the project id. Set the EU or self-hosted URL if you are not on US Cloud.

In Telara

Connect in Telara

API key

PostHog personal API key for project APIs. Store project_id with the credential; optionally set base_url for EU Cloud or self-hosted instances.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • Personal Api Key

Knowledge

What gets indexed

ResourceCoverage
ProjectsPartial — not every record the vendor holds is synced
DashboardPartial — not every record the vendor holds is synced
Feature flagPartial — not every record the vendor holds is synced
ExperimentPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ProjectsUp to 1 dayRemoved records disappear on the next full sync
DashboardUp to 1 dayRemoved records disappear on the next full sync
Feature flagUp to 1 dayRemoved records disappear when Telara next reconciles that resource
ExperimentUp to 1 dayRemoved 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: Projects, Dashboard, Feature flag, Experiment.

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

Project API keys meant for capture (phc-…) are the wrong class. Use a personal API key.
The wrong region URL looks like a 401.