Data & Storage · Integration
PostHog
Add PostHog to your product for your customers, and give your AI agents governed access to it.
PostHog is event-first, so the record that matters is the event and the person it is attached to, and almost everything else is derived from those two. That shapes the integration: you are usually reading a query result rather than a table, because insights are computed rather than stored. Feature flags are the part most products want to write against, since evaluating a flag per customer is what makes a rollout controllable. There are separate US and EU clouds with different hosts, which matters more than it sounds: pointing a European customer at the US host is a data-residency problem rather than a latency one. fastn keeps each customer's project key scoped to them and handles the regional host.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own PostHog project so product analytics appear inside your product without you re-implementing them.
Read events and persons per tenant to show behaviour next to the workflow your product already owns.
Evaluate feature flags per customer so a rollout can be controlled from your product.
Query an insight and render the result, rather than exporting raw events and recomputing them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries recent events for a person before explaining what a user actually did.
An agent toggles a feature flag within governed permissions, with the change audited per tenant.
An agent reads an insight and reports which step of a funnel is losing people.
Example prompt
What did this user do in the hour before they cancelled, and which flags were enabled for them?
Set up PostHog in 4 steps
- 01Enable the PostHog connector from your fastn dashboard.
- 02Have each customer authorise their own PostHog account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the PostHog integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PostHog integration without building it. Your customers connect their own PostHog account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a PostHog update is not your on-call problem.
- One integration serves your product and your agents. The same governed PostHog connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Mixpanel
Amplitude
SegmentOften used alongside
Tools the same teams tend to run next to PostHog, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FacePostHog integration FAQ
How do I add a PostHog integration to my product?
Enable the PostHog connector in your fastn dashboard, then let each customer authenticate their own PostHog account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PostHog client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PostHog account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PostHog account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this PostHog integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent queries recent events for a person before explaining what a user actually did.
Who maintains the PostHog integration?
fastn does. When PostHog changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the PostHog integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large PostHog reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the PostHog integration?
A common starting point: let a customer connect their own PostHog project so product analytics appear inside your product without you re-implementing them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the PostHog integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PostHog does not change your per-connector cost. You can start free with 3 connected accounts.
Add PostHog to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.