PostHog
Last updated 2026-06-14
What this unlocks
Connect PostHog and Quri reads your product analytics — events, pageviews, and conversion trends — so it can answer questions and alert you when a key product metric moves, without you opening the PostHog dashboard.
Connect it in Quri
- Open /app/connect in Quri and choose PostHog from the list of sources.
- Paste your PostHog project API key and your instance host into the connect form.
- Save the connection so Quri can reach your project and read its data.
- Wait for the first sync — your PostHog metrics appear in Quri once it completes.
Get your credentials
- Sign in to PostHog and open Project settings for the project you want Quri to read.
- Copy the Project API key shown under the project settings.
- Note your instance host — app.posthog.com (US), eu.posthog.com (EU), or your self-hosted URL.
- Keep both values handy; you paste them into Quri at /app/connect.
Access Quri reads with
- Read-only access to your PostHog project events and insights — Quri never writes to PostHog.
- The project API key scopes access to that one project, not your whole PostHog organization.
Troubleshooting
- Quri says it cannot reach my PostHog project — what should I check?
- Confirm the host matches your instance: app.posthog.com for US Cloud, eu.posthog.com for EU Cloud, or your exact self-hosted URL. A US key against the EU host (or the reverse) will fail to connect.
- Why does PostHog not open a sign-in window like some other sources?
- PostHog connects with a project API key and host rather than OAuth, so you paste those two values into Quri instead of approving a pop-up. It is the standard way PostHog grants programmatic read access.
- I connected PostHog but no metrics have shown up yet.
- The first sync can take a few minutes. If it stays empty, re-check the API key and host at /app/connect, and make sure the project actually has events — Quri can only read data PostHog already holds.