suggesting-data-imports

Guide importing external data into the PostHog data warehouse.

58|5|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/PostHog/skills --skill suggesting-data-imports
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suggesting-data-imports
Source: https://github.com/PostHog/skills/tree/main/skills/omnibus/suggesting-data-imports
Command: npx skills add https://github.com/PostHog/skills --skill suggesting-data-imports

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, production database tables, or other data that PostHog does not collect natively. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, etc.), production databases (Postgres, MySQL, BigQuery, Snowflake), and other arbitrary data sources. Covers checking existing sources, identifying the right source type, and guiding the setup.

Core Features & Use Cases

  • Guides identification of external data needs and connections into a data warehouse for PostHog.
  • Outlines source-type mapping (Stripe, Hubspot, Zendesk, databases) and prefixes for imported tables.
  • Provides a step-by-step workflow to check existing connections, select sources, and plan imports, enabling combined analysis of PostHog events with external data.

Quick Start

Identify the external data needs and start the data-warehouse connection workflow to import relevant data sources.

Frequently Asked Questions about suggesting-data-imports

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import external data from Stripe or Hubspot into PostHog for analysis?

To import external data into PostHog, you connect SaaS tools like Stripe or Hubspot through the PostHog data warehouse. This workflow guides you through checking existing connections, selecting the right data source type, and proposing concrete import steps.

Why does my PostHog query fail when searching for revenue or billing data?

A PostHog query fails when searching for revenue or billing data because that information lives in external systems not natively collected. You need to identify the missing external data and import it via the data warehouse to enable combined analysis.

Can I connect production databases like Postgres or Snowflake to the PostHog data warehouse?

Yes, the PostHog data warehouse can import from production databases including Postgres, MySQL, BigQuery, and Snowflake. It maps the source type, applies prefixes to imported tables, and guides the setup to make the data queryable.

What is the best way to analyze CRM deals alongside PostHog product events?

The best way to analyze CRM deals with PostHog events is importing the CRM data into the data warehouse. By connecting external sources like Salesforce, you bridge mismatched schemas and combine external deal data with native product analytics.

How do I check existing data sources before setting up a new data import?

Before setting up a new data import, this workflow enforces a structured check of your existing data warehouse connections. It verifies currently synced sources to prevent duplicate data imports and identifies missing tables required for your analysis.

When should I not use the data warehouse for external data integration?

You should not use the data warehouse for external data integration if your query targets data PostHog already collects natively. It is specifically designed for external systems, missing tables, or mismatched schemas requiring import to enable analysis.