Search and data
PostHog for AI agents.
Managed auth, ready-made tools.
Query product analytics, read insights and dashboards, and manage feature flags in PostHog on behalf of each of your users.
About PostHog
With the PostHog connector, your agent works with each user’s own PostHog projects. It can run an analytics query, read insights and dashboards, look up persons and list, create or update feature flags, using only the tools your project allows.
PostHog is a product analytics platform with feature flags, session replay and experiments.
Tools
What your agent can do in PostHog.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own PostHog connection.
-
Run a query
Readposthog_run_queryRun a HogQL query on the project's events.
-
List insights
Readposthog_list_insightsList the saved insights in a project.
-
List dashboards
Readposthog_list_dashboardsList the dashboards in a project.
-
List persons
Readposthog_list_personsSearch and list persons.
-
List feature flags
Readposthog_list_feature_flagsList the feature flags in a project.
-
Create a feature flag
Writeposthog_create_feature_flagCreate a new feature flag.
-
Update a feature flag
Writeposthog_update_feature_flagChange a flag's rollout or turn it on or off.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in PostHog, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent query data and read flags, and switch off
posthog_update_feature_flagso it can never change a rollout. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example queries and insights but not feature flags. A call outside them is refused.
Get started
Connect PostHog
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect PostHog
Each end user authorizes their own PostHog account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own PostHog account, once. const connection = await agent200 .user("user_123") .connect("posthog"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the PostHog tools
Name the user, the model and the tools. The model decides which PostHog tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How many users signed up last week", tools: ["posthog"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on PostHog's own sign-in page. You never see or store their PostHog password.
-
What access is requested
The scopes the connection needs, such as reading insights or writing feature flags, listed on PostHog's authorization screen. Users can remove the app later from their PostHog account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the PostHog connector and how to use it.
Connector: PostHog, through Agent200. In code: "posthog". What it does: Query product analytics, read insights and dashboards, and manage feature flags in PostHog on behalf of each of your users. Page: https://www.agent200.com/connectors/posthog/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on PostHog's own page, through the authorization link Agent200 returns. Never ask a user for a PostHog password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: posthog_run_query, posthog_list_insights, posthog_list_dashboards, posthog_list_persons, posthog_list_feature_flags. Write tools: posthog_create_feature_flag, posthog_update_feature_flag. Name "posthog" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/posthog/framework/claude/ https://www.agent200.com/connectors/posthog/framework/chatgpt/ https://www.agent200.com/connectors/posthog/framework/claude-code/ https://www.agent200.com/connectors/posthog/framework/muse/ https://www.agent200.com/connectors/posthog/framework/grok-bot/ https://www.agent200.com/connectors/posthog/framework/openai-dots/ https://www.agent200.com/connectors/posthog/framework/claude-duet/ https://www.agent200.com/connectors/posthog/framework/hermes-agent/ https://www.agent200.com/connectors/posthog/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/posthog.md
Guides
Use PostHog with the AI you build on.
Step-by-step setup for PostHog with a specific model, assistant or agent framework.
-
PostHog + Claude
How to connect PostHog to Claude
-
PostHog + ChatGPT
How to connect PostHog to ChatGPT
-
PostHog + Claude Code
How to connect PostHog to Claude Code
-
PostHog + Muse
How to connect PostHog to Muse
-
PostHog + Grok Bot
How to connect PostHog to Grok Bot
-
PostHog + OpenAI Dots
How to connect PostHog to OpenAI Dots
-
PostHog + Claude Duet
How to connect PostHog to Claude Duet
-
PostHog + Hermes Agent
How to connect PostHog to Hermes Agent
-
PostHog + OpenClaw
How to connect PostHog to OpenClaw
FAQ
PostHog and Agent200, answered.
Who handles the PostHog OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for PostHog.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's PostHog connection, never another user's. It cannot reach anything the user or PostHog has not authorized.
Can I limit what my agent can do in PostHog?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.