Posthog Connector
posthog_connectorPostHog product analytics: account/project info, raw events, person records, event definitions, HogQL queries, and funnel conversion analysis. Read-only via Personal API key (Path A). When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | get_account_info: Get PostHog account and project metadata for the connected user. Returns the user email, organization name, project ID, | list_events: List recent raw events captured by PostHog for the project. Returns event ID, event name, distinct ID, timestamp, the fu | list_persons: List person records for the PostHog project. A person is PostHog's unified user record, aggregating events from one or m | get_event_definitions: List event-name definitions for the project — the event catalog that tells you what event names can actually be queried | run_query: Execute a HogQL query against PostHog events and persons. HogQL is PostHog's SQL-like query language — use it for compou | get_funnel: Compute a funnel over an ordered list of event steps. Returns the per-step user count, the conversion rate from the firs | |
| params | No | Action-specific parameters. get_account_info: none | list_events: {project_id?: integer, event?: string, after?: string, before?: string, limit?: integer} | list_persons: {project_id?: integer, search?: string, limit?: integer} | get_event_definitions: {project_id?: integer, search?: string, limit?: integer} | run_query: {query: string, project_id?: integer, limit?: integer} | get_funnel: {steps: array, project_id?: integer, date_from?: string, date_to?: string} |