Skip to content

Analytics

PostHog
API integration

Ship Analytics features without building the integration. Full PostHog API access via Proxy, normalized data through Unified APIs, and 10+ MCP-ready tools for AI agents — all extensible to your exact use case.

Talk to us
PostHog

Use Cases

Why integrate with PostHog

Common scenarios for SaaS companies building PostHog integrations for their customers.

01

Sync PostHog persons and groups into your product's user directory

If you're building a CRM, customer success platform, or revenue tool, you can pull PostHog's Persons (users) and Groups (organizations) into your product so your customers see real account structures alongside product usage context — without building a custom PostHog integration from scratch.

02

Enrich support workflows with PostHog user context

Helpdesk and support platforms can map their user records to PostHog Persons, giving agents instant visibility into who the user is, which organization they belong to, and their associated properties — all surfaced natively in the support UI.

03

Power account-level health scoring with organization data

Customer success and revenue intelligence platforms can pull PostHog Group (organization) data to build product health scores, identify at-risk accounts, and give account executives real context about how a company is using the product.

04

Build AI-powered copilots with user and org awareness

AI agent platforms and copilot products can query PostHog user and organization data to ground their responses in real context — knowing who the user is, what organization they belong to, and their properties before generating recommendations or troubleshooting steps.

05

Automate user and organization provisioning across tools

Workflow automation and iPaaS products can sync PostHog's user and organization directory with other systems, ensuring that when a new person or group appears in PostHog, downstream tools stay in sync without manual intervention.

What You Can Build

Ship these features with Truto + PostHog

Concrete product features your team can ship faster by leveraging Truto’s PostHog integration instead of building from scratch.

01

Account directory sync from PostHog Groups

Automatically import PostHog Groups (organizations) into your platform so customers see their real account hierarchy without manual CSV uploads.

02

User identity resolution panel

Surface PostHog Person properties — like email, name, and custom traits — directly inside your product's user detail view, giving your customers a unified profile.

03

Organization-aware feature gating

Pull PostHog Group properties (e.g., subscription tier, plan type) into your platform to drive access controls, entitlements, or tiered feature visibility for end users.

04

Cross-platform user directory search

Let your customers search and browse PostHog Persons and Groups alongside users from other connected tools using Truto's Unified User Directory API.

05

Account context cards for sales and support

Display a compact PostHog organization card — showing group properties and associated users — inside CRM deal views or support ticket sidebars.

SuperAI

PostHog AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_post_hog_me

Get the authenticated PostHog user's profile and settings via the @me shortcut. Returns the user record including its id and attributes defined by the upstream User schema. No required parameters.

list_all_post_hog_members

List members of a PostHog organization. Returns: id, user, level, joined_at, updated_at, is_2fa_enabled, has_social_auth, last_login, search_match_type. Required: organization_id.

list_all_post_hog_projects

List comments and tasks across a PostHog project, filterable by scope, item, kind, author, or search text. Returns comment records with id, content, kind, scope, created_by, and completion fields. Required: project_id.

list_all_post_hog_actions

List PostHog actions in a project. Returns: id, name, description, tags, post_to_slack, steps, created_at, created_by. Required: project_id.

list_all_post_hog_annotations

List PostHog annotations for a project, covering dashboard and insight annotations. Returns: id, content, date_marker, creation_type, dashboard_item, dashboard_id, dashboard_name, insight_short_id, insight_name, insight_derived_name, created_by, created_at, updated_at, deleted, scope, emoji, hidden_in_user_interface. Required: project_id.

list_all_post_hog_cohorts

List the cohorts defined in a PostHog project. Returns: id, name, description, groups, deleted, filters, query, version, pending_version, is_calculating, created_by, created_at, last_calculation, last_backfill_person_properties_at, last_error_message, count, last_import_total_count, search_match_type, and 7 more. Required: project_id.

list_all_post_hog_dashboards

List dashboards in a PostHog project. Returns each dashboard with id, name, description, pinned, created_at, created_by, folder, and tags. Required: project_id.

list_all_post_hog_event_definitions

List event definitions of a PostHog project. Returns: id, name, description, tags, verified, last_seen_at, created_at, updated_at. Required: project_id. On projects with 50,000+ event definitions, counts cap at 10,000 unless search, exclude_stale, verified, names, tags, or event_type=event_posthog is set.

list_all_post_hog_events

List and filter PostHog events captured in a project. Returns: id, event, distinct_id, properties, timestamp, person, elements, elements_chain. Required: project_id.

list_all_post_hog_groups

List all groups of a specific group type in a PostHog project. Returns: id, group_key, group_type_index, properties, created_at. Required: project_id, group_type_index. Pagination is forward-only by cursor; the previous page is always null.

list_all_post_hog_insights

List insights in a PostHog project. Returns: id, short_id, name, query, result, created_at, tags, last_viewed_at. Required: project_id.

list_all_post_hog_persons

List persons in a PostHog project. Returns each person's id, name, distinct_ids, properties, created_at, last_seen_at, uuid, and matched_fields. Required: project_id. Read-only through this endpoint; create or update persons via the capture API or SDKs instead.

list_all_post_hog_property_definitions

List PostHog property definitions for a project. Returns: id, name, property_type, is_numerical, verified, updated_at. Required: project_id.

list_all_post_hog_surveys

List PostHog surveys configured for a project. Returns each survey with its id, name, type, questions, conditions, and created_at. Required: project_id.

list_all_post_hog_group_types

List the group types configured for a PostHog project. Returns each group type with its group_type_index, the value to pass as group_type_index when listing or filtering groups. Required: project_id.

list_all_post_hog_session_recordings

List PostHog session recordings for a project. Returns: id, distinct_id, viewed, viewers, recording_duration, start_time, end_time, click_count, ongoing. Required: project_id.

Why Truto

Why use Truto’s MCP server for PostHog

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1000+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

Unified APIs

Unified APIs for PostHog

Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.

Unified User Directory API

Organizations

Organizations are the top level entity in the source application. Users are associated with an organization.

View Docs

Users

The User object represents a User.

View Docs

How It Works

From zero to integrated

Start with PostHog in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s PostHog account

Use Truto’s frontend SDK to connect your customer’s PostHog account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call PostHog

Truto’s Proxy API is a 1-to-1 mapping of the PostHog API. You call us, we call PostHog, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate PostHog’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about PostHog on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

What Truto Unified APIs are available for PostHog?

PostHog is supported through Truto's Unified User Directory API, which provides standardized access to Organizations (mapped from PostHog Groups) and Users (mapped from PostHog Persons). Additional tools and API resources can be built on request.

How does authentication work for PostHog integrations via Truto?

PostHog's API uses personal API keys or project API keys for authentication. Truto handles credential storage and auth management so your end users can connect their PostHog accounts securely without you building a custom auth flow.

Does PostHog have rate limits that affect integration performance?

Yes, PostHog enforces rate limits on its API endpoints. Truto manages pagination and request throttling automatically, so your integration handles large datasets without hitting limits or requiring manual retry logic.

Can I access custom properties on PostHog Persons and Groups?

PostHog allows arbitrary custom properties on both Persons and Groups. Truto's Unified User Directory API maps standard fields, and custom properties can be accessed as additional data. If you need specific custom field mappings, Truto can build tailored support on request.

What if I need PostHog data beyond users and organizations — like events, session replays, or feature flags?

Currently, the Unified User Directory API covers Organizations and Users. PostHog's API also exposes events, session recordings, feature flags, insights, and more. Truto can build custom tools for these endpoints on request to match your specific integration needs.

Does Truto support both PostHog Cloud and self-hosted instances?

PostHog can be deployed as a cloud service (us.posthog.com / eu.posthog.com) or self-hosted. Truto can be configured to point at your end users' specific PostHog instance URL, supporting both deployment models.

PostHog

Get PostHog integrated into your app

Our team understands what it takes to make a PostHog integration successful. A short, crisp 30 minute call with folks who understand the problem.