Stats
Actions
Tags
From posthog
Identifies when users need to import external data (Stripe, databases, etc.) into PostHog and guides setup via the data warehouse.
How this skill is triggered — by the user, by Claude, or both
Slash command
/posthog:suggesting-data-importsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps identify when data the user needs lives outside PostHog and guides them toward importing it via the data warehouse. The key insight is recognizing the gap — then connecting it to the right source type.
This skill helps identify when data the user needs lives outside PostHog and guides them toward importing it via the data warehouse. The key insight is recognizing the gap — then connecting it to the right source type.
PostHog collects product analytics events, persons, sessions, and groups via its SDKs. Additional products are available but must be enabled: session replay, feature flags, experiments, surveys, web analytics, error tracking, AI observability, conversations, logs, revenue analytics, workflows, CDP destinations, and batch exports. PostHog does not collect external business data like payments, subscriptions, CRM records, support tickets from other systems, or production database tables — that data must be imported via the data warehouse.
Listen for signals that the user needs external data:
If a query failed, check the error — if it's "table not found" or similar, the data likely needs to be imported.
Call posthog:external-data-sources-list to see existing sources. The data might already be imported but the user doesn't know the table name or prefix.
If a source exists for the system they're asking about, call posthog:external-data-schemas-list to show the available tables. The data might be there but under a different name or prefix.
Also call posthog:read-data-warehouse-schema to see all queryable tables — the data might already be available as a view or joined table.
If the data isn't imported yet, call posthog:external-data-sources-wizard to see available source types. Match the user's need to a source:
Common patterns:
| User wants | Source type | Key tables |
|---|---|---|
| Revenue / payment data | Stripe, Chargebee, Shopify | charges, subscriptions, invoices, customers |
| CRM / sales pipeline | Hubspot, Salesforce, Attio | contacts, deals, companies |
| Support tickets | Zendesk | tickets, users, organizations |
| Product data from their DB | Postgres, MySQL, BigQuery, Snowflake, Redshift | user's own tables |
| Marketing / ads | Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads | campaigns, ad_groups, ads |
| Email marketing | Mailchimp, Klaviyo | campaigns, lists, subscribers |
| Project management | Linear | issues, projects |
| Error tracking (external) | Sentry | issues, events |
Present the recommendation concisely:
Example: "Your Stripe data isn't in PostHog yet. If you connect a Stripe source, you'll get tables like charges, subscriptions, and customers that you can join with PostHog events to analyze revenue by user behavior."
If the user wants to proceed, the fastest path is the one-step data-warehouse-source-setup tool (validate creds →
discover tables → sync defaults → create, in one call), with data-warehouse-source-connect-link to collect
credentials securely in the browser rather than in chat. For anything beyond the happy path (hand-picking tables,
non-default sync types, webhooks, CDC), hand off to the setting-up-a-data-warehouse-source skill, which covers
the full flow, sync-type selection, webhook registration, and prefix guidance. Do not duplicate that workflow here.
Once connected, help the user write their first query joining PostHog data with the imported data. Use posthog:execute-sql to demonstrate.
Common join patterns:
SELECT * FROM stripe_customers sc JOIN persons p ON sc.email = p.properties.$emailposthog:read-data-warehouse-schema and posthog:external-data-schemas-list before saying data doesn't exist.stripe_charges not charges). The user might not know the prefix.data-warehouse-source-connect-link to hand the user a browser link — it opens a minimal connect page rendering the source's full connection form (OAuth or credentials, whichever the source offers) that stashes the details temporarily without creating the source. Afterwards pass {"credential_id": <id>} (discovered via data-warehouse-stored-credentials-list) to data-warehouse-source-setup — stored credentials are single-use and expire after 24 hours. Don't collect passwords or OAuth tokens in chat.posthog:external-data-sources-list: Check existing source connectionsposthog:external-data-schemas-list: Check what tables are already importedposthog:read-data-warehouse-schema: See all queryable tables including viewsposthog:external-data-sources-wizard: Get available source typesposthog:data-warehouse-source-connect-link: Get a secure browser/OAuth link to collect credentialsposthog:data-warehouse-source-setup: One-step create (validate, discover tables, apply sync defaults, create)posthog:execute-sql: Run queries to demonstrate what's possiblesetting-up-a-data-warehouse-source: Full source creation workflow — hand off here once the user decides to connect a sourcenpx claudepluginhub anthropics/claude-plugins-official --plugin posthogGuides connecting external data sources (Postgres, Stripe, etc.) to PostHog warehouse. Covers source discovery, credential validation, table selection, sync type configuration, and creation.
Exports marketing data (metrics, contacts, campaigns, performance snapshots) to BigQuery, Google Sheets, or Supabase for analysis and reporting. Supports PII redaction, custom schemas, and append/replace modes.
Drives Google Analytics (GA4), Google Tag Manager, Google Search Console, and BigQuery from chat for tracking plans, reports, conversion setup, audits, and SQL queries.