Capability

PostHog Analytics

What your agent can do with it

  • posthog_apiAuthenticated READ access to the pod's PostHog project. `config.baseUrl` pins host + project id at install time; `config.auth` injects the vaulted Personal API Key as `Authorizati…
  • posthog_get_event_trendEvent volume over time for ONE named event — the number a landing page or a feature is judged by. Reads PostHog's trend insight, so the series is computed server-side rather than …
  • posthog_list_recent_eventsThe most recent raw events, newest first — what is actually arriving right now, with each event's name, timestamp, distinct_id and properties. Use this to confirm instrumentation …
  • posthog_list_personsThe people behind the events — PostHog person records with their distinct ids and properties. Use it to answer "who are my users", not just "how many". Args: { limit?: number (def…
  • posthog_list_saved_insightsThe insights and dashboards already saved in this project. Read this FIRST when asked an analytics question — a saved insight is the project's own agreed definition of a metric, a…

What you will need

Asked for at install. Stored in your pod, never on our servers.

  • PostHog Personal API KeyA PostHog PERSONAL API KEY (PostHog → Settings → Personal API keys) with query:read, insight:read, event:read and person:read. Stored server-encrypted in the v…
  • PostHog hostOrigin of the PostHog instance — e.g. https://analytics.synap.live (self-hosted) or https://us.posthog.com (Cloud). Baked into the installed tool's baseUrl.
  • PostHog project idNumeric id of the PostHog project that belongs to THIS pod (2 for the Synap org). Baked into the installed tool's baseUrl and deliberately NOT a call parameter…
  • {{name}} PostHog Personal API KeySecretPostHog Personal API Key, read scopes only. The analytics belong to the pod, so this is pod-wide: every pod member and every agent reads the same project throu…