Skip to content

PostHog

Product usage, through the insights your team has already saved. Read-only.

Connects with Personal API key
Reads 5 operations
Writes None
Irreversible None
Personal data None. No person-level records.
Data stays in AWS Sydney (ap-southeast-2)
  • The projects the key can reach.
  • Event definitions (the event names a project has seen, and when each was last observed) and property definitions.
  • Saved insights: the charts your team has already built, with their filters, breakdowns and date ranges, and the result PostHog last computed for each.

StoriBot prefers a saved insight to reconstructing a question from raw definitions, so the numbers it reports match the ones your team already looks at.

Raw events and individual person profiles. StoriBot reads definitions and saved insights, not the event stream.

Nothing. There are no write operations in this connector.

Connect with a personal API key. In PostHog, open Settings, then Personal API keys, and create a key with read scopes only: project, insight, event definition and property definition. It starts with phx_.

  • The region the project lives in: US or EU. A key is valid in one region only.
  • The personal API key.

These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.

All 5 operations
Operation Kind What it does
list_projects Read List the projects this key can reach, with their numeric ids.
list_event_definitions Read List the event names a project has seen, with when each was last observed.
list_property_definitions Read List a project’s property definitions, each with its name and the type of value it holds.
list_insights Read List the project’s saved insights, the charts the customer has already built and named, each with the filters, breakdown and date range they chose.
get_insight Read Retrieve one saved insight with its cached result.