AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

querying-posthog-data

Explains how to query PostHog data, defaulting to typed runners for supported product analytics. Read it before you write HogQL/SQL. Also read it before you call execute-sql against PostHog. Use it to find or aggregate PostHog entities. These entities include insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, warehouse data, and persons. Use it for trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, and LLM traces. Before you calculate a governed business or telemetry measure, check system.information_schema.metrics for an approved definition. Examples include MRR, activation, billable usage, active organizations, and failure rates. Use the approved definition before you derive a measure from raw events or use a typed domain tool. It also covers HogQL differences, system table schemas, functions, query examples, and schema discovery.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--querying-posthog-data at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 65

references/models-integrations.md

Integrations

Integration (system.integrations)

Third-party service connections configured per project. Each integration represents a connection to an external service like Slack, GitHub, Salesforce, or an ad platform.

Columns

| Column | Type | Nullable | Description | | ---------------- | ----------------- | -------- | ----------------------------------------------------------------------------------- | | id | integer | NOT NULL | Primary key (auto-generated) | | team_id | integer | NOT NULL | Team this integration belongs to | | kind | varchar(32) | NOT NULL | Integration type identifier (see below) | | integration_id | text | NULL | Identifier in the external system (e.g. Slack workspace ID, GitHub installation ID) | | config | jsonb | NOT NULL | Non-sensitive, kind-specific configuration | | errors | text | NOT NULL | Error message if the integration has issues, empty string otherwise | | created_at | timestamp with tz | NOT NULL | Creation timestamp | | created_by_id | integer | NULL | Creator user ID |

Integration Kinds

slack, salesforce, hubspot, google-pubsub, google-cloud-storage, google-ads, google-sheets, google-cloud-service-account, snapchat, linkedin-ads, reddit-ads, tiktok-ads, bing-ads, intercom, email, linear, github, gitlab, meta-ads, twilio, clickup, vercel, databricks, azure-blob, firebase, jira, pinterest-ads

Key Relationships

  • Integrations belong to a Team (team_id)
  • Integrations are referenced by Hog functions, Batch exports and Workflows that use external services

Important Notes

  • sensitive_config (encrypted credentials, tokens) is deliberately not exposed in this table
  • config structure varies by integration kind and may include account names, workspace IDs, or other non-secret metadata
  • Each (team_id, kind, integration_id) combination is unique
  • Most integrations are created via OAuth flows or file uploads, not direct API calls