Data pipelines
Contents
Data pipelines is how you move data from one place to another. You can move data independently without it touching any other PostHog tools, or in and out of PostHog. It works with both your PostHog data – events, persons, sessions, and groups – and data from external tools like Stripe, HubSpot, or your own Postgres database.
It's made up of three parts:
- Sources move data from anywhere to anywhere, including syncing data from external tools and databases into PostHog, so you can query it alongside your product data.
- Transformations add, edit, or drop event properties as events are ingested.
- Destinations send data out of PostHog – events to tools like Slack or HubSpot in realtime, batch exports of your PostHog data to a warehouse, or synced source data written to your own database.
Realtime destinations and transformations are built from Hog functions, which you can configure from a template, write yourself, or have PostHog AI write for you.
Where you can use it
Build and monitor pipelines in the PostHog web app, or create and debug functions from an MCP client or your own systems.
PostHog Web
Configure sources, transformations, and destinations, then watch logs and metrics for each one.
Build a pipeline →PostHog MCP
Create, update, test-invoke, and debug pipeline functions from any MCP client or AI editor.
Manage pipelines →API
Manage Hog functions and batch exports programmatically, so pipelines live in your own config.
Use the API →What's included
Data pipelines covers the data already in your PostHog project and anything you connect from outside it. Sources bring external data in, transformations reshape events during ingestion, and destinations send both PostHog and source data back out.
Sources
Sync data from hundreds of tools and databases, upload a file, or push it in yourself with an incoming webhook.
Link a source →Transformations
Add, edit, or drop event properties during ingestion, before anything is stored.
Transform events →Destinations
Send events to other tools as they happen, batch export PostHog data to your warehouse, or write source data to your own database.
Send data out →Common use cases
Teams most often use data pipelines to bring revenue and CRM data from tools like Stripe and HubSpot into PostHog, to keep a warehouse in sync with product data, to push events into tools like Slack, HubSpot, or Intercom over webhooks, and to enforce a schema at ingestion so bad events never make it into analytics.
Transformations also help you label events on the way in – setting a property like user_tier or page_category – which makes downstream metrics and SQL queries much easier to write.