PostHog integration

Give Fin product analytics context from PostHog


Overview

Configure a Data connector to expose PostHog analytics data to Fin (session data, feature flags, and cohort membership), giving Fin the product context it needs to resolve queries accurately.

On Intercom, you set up the PostHog connection in the same workspace as your Helpdesk inbox, tickets, and reporting, and Fin hands off to your team there with the full conversation.

What you can do

  • Expose PostHog user session data and event history to Fin via Data connector
  • Let Fin reference feature flag states and cohort membership in answers
  • Use product usage context to give more relevant support responses
  • Use PostHog data in Fin conversations, Workflows, and Procedures
  • Requires JWT or email OTP user authentication for live use in production

How it works

Go to Fin AI Agent → Train → Tasks → Manage Data connectors and create a custom connector for PostHog, or start from an AI recommendation.

Set up the API call to your PostHog system. Configure request parameters, authentication (token-based or OAuth), and map the response fields Fin should use.

Data connectors require JWT or email OTP user authentication to go live. Connectors can only be fully tested in production, not in test workspaces.

PostHog MCP for Operator and Copilot

Operator pulls information from PostHog over MCP while it analyzes Fin's performance and proposes improvements for your team to review. This connection is coming soon.

Copilot pulls information from PostHog over MCP to help your team find answers in the Inbox. Copilot is in closed beta. This connection is coming soon.

Configure

Works with Fin through an API Data connector, supporting both read and write operations. Fin can fetch data to personalize answers and execute actions like processing refunds, updating accounts, or modifying subscriptions in connected systems.

Read the full setup documentation →