:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Searching for existing entities
"find / which / do we have / what's our X chart" questions about PostHog-created entities are SQL searches against system.* (system.insights, system.dashboards, system.cohorts, system.feature_flags, system.experiments, system.surveys, system.notebooks), not *-list walks.
This routing is for finding saved artifacts (a chart, dashboard, cohort, flag). "What data / tables / events do we have available?" is a schema question instead — answer it from system.information_schema.tables (and read-data-schema for events), not by searching system.insights.
Required order on every run, no shortcuts — schema first, every run:
- Confirm the table's columns with an
execute-sqlagainstsystem.information_schema.columns, e.g.SELECT column_name, data_type, description FROM system.information_schema.columns WHERE table_name = 'system.insights'. Schema markdown in skills/references (models-*.md,querying-posthog-datadocs) is documentation, not a substitute — query the schema. execute-sqlagainstsystem.*— uses only columns confirmed in step 1.<entity>-get(e.g.insight-get,dashboard-get) — verifies the entity shape; do NOT re-execute-sqlby ID.