Skip to Content
ResourcesIntegrationsDeveloper ToolsPostHog

PostHog

Service domainPRODUCT ANALYTICS
PostHog icon
Arcade Optimized

Arcade.dev LLM tools for PostHog analytics

Author:Arcade
Version:1.0.1
Auth:No authentication required
41tools
41require secrets

PostHog is a product analytics and experimentation platform. The Arcade PostHog toolkit lets agents query analytics, manage experiments, and curate insights directly from a PostHog project.

Capabilities

  • Build and manage dashboards, insights, funnels, trends, and retention views.
  • Create and iterate on experiments, feature flags, and surveys with full CRUD support.
  • Inspect event and property definitions, investigate errors, and compare time periods.
  • Run ad-hoc HogQL or insight queries and retrieve results for downstream analysis.

OAuth

No OAuth — authentication uses a PostHog personal API key passed as a secret.

Secrets

  • POSTHOG_PERSONAL_API_KEY — PostHog personal API key created under Account Settings → Personal API Keys.
  • POSTHOG_SERVER_URL — target PostHog region or self-hosted instance URL (e.g. https://us.posthog.com).

Configure both in the Arcade Dashboard per the Arcade secret setup guide.

Available tools(41)

41 of 41 tools
Operations
Behavior
Tool nameDescriptionSecrets
Pin an existing insight as a tile on a dashboard.
1
Compare the same metric across two date ranges side-by-side.
1
Create a new empty dashboard. Insights can be pinned to it as tiles afterward.
1
Create an A/B test experiment. Before creating, verify the feature_flag_key is not already in use and confirm the event names for metrics are valid. Note: PostHog does not enforce unique feature_flag_key values across experiments. Duplicate keys will not error but will cause unpredictable behavior.
1
Create a feature flag and an experiment in one step. The flag is created with the specified rollout_percentage, then the experiment is linked to it. Note: PostHog does not enforce unique feature_flag_key values across experiments. Duplicate keys will not error but will cause unpredictable behavior.
1
Create a new feature flag. Verify the key is not already in use to avoid duplicates. After creation, consult PostHog SDK documentation for the user's language/framework to integrate the flag.
1
Save a tested query as a reusable insight. Always verify the query produces expected results before saving it as an insight. The query_id is not validated by PostHog — ensure it is a valid cache_key from a previously executed query. Passing an invalid query_id will create a broken insight.
1
Create a new survey. Verify the name is not already in use to avoid duplicates. After creation, consult PostHog SDK documentation to integrate the survey into the user's application.
2
Soft-delete a dashboard by ID. The dashboard is marked as deleted but can be restored.
2
Soft-delete an experiment by ID (marks as archived). Important: archiving an experiment does NOT unlink its feature flag. PostHog still considers the flag as linked to an "active" experiment, blocking flag deletion. To fully clean up, delete the flag separately after the experiment is archived.
1
Soft-delete a feature flag by numeric ID or key. Provide one of flag_id or flag_key. Note: flags linked to an experiment cannot be deleted until the experiment is concluded and deleted first. PostHog considers even archived experiments as "active" for flag linkage purposes.
1
Soft-delete an insight by ID.
2
Soft-delete a survey by ID (marks as archived).
2
Get the activity log across all surveys. Returns a chronological list of changes made to any survey (created, updated, archived, etc.), not response metrics.
2
Get a dashboard's full configuration including all insight tiles. Provide dashboard_id or dashboard_name.
1
Get stack trace, occurrence count, and affected users/sessions for a specific error.
2
Get an experiment's full configuration. Includes variants, metrics, and current status. Provide either the numeric ID or the name.
1
Get experiment results including metric data and exposure counts. Only available for launched experiments that have collected data. Draft, not-yet-launched, or legacy experiments return 404.
1
Get a feature flag's full definition including rollout rules. Provide either the numeric ID or the flag key.
2
Build a multi-step conversion funnel with optional property breakdowns.
1
Get an insight's full configuration and current query results. Provide either the numeric ID or the name.
1
Get cohort retention data showing what percentage of users return. Shows return rates after a user's initial event.
1
Get a survey's full configuration. Includes questions, targeting rules, and scheduling. Provide either the numeric ID or the name.
2
Get the activity log for a survey. Returns a chronological list of changes made to the survey (created, updated, archived, etc.), not response metrics.
1
Get a time-series trend for an event over a date range. Optionally broken down by a property.
1
Page 1 of 2(25 of 41)
Last updated on