Use PostHog's Hubspot data pipeline destination: open Data pipeline, then Destinations, search for Hubspot, click + Create, connect your HubSpot account and press Create & Enable. It sends PostHog person data into your HubSpot Contacts list. For a custom flow, use the webhook destination or edit the destination's Hog code.
What the Hubspot destination sends
PostHog's Hubspot destination sends PostHog person data to HubSpot, populating your Contacts list. It suits product-led businesses that want sales or marketing to see who's using the product, without exporting CSVs. PostHog's page doesn't set out a field-by-field map or describe a sync back the other way, so treat it as person data flowing from PostHog into HubSpot.
You'll need access to the relevant HubSpot account to set it up, since the connection step asks you to authorise it.
Setting it up in PostHog
- In PostHog, click the Data pipeline tab in the left sidebar.
- Click the Destinations tab.
- Search for Hubspot and click + Create.
- Connect your HubSpot account at the configuration step.
- Add any event, property or SQL filters, and use the test interface.
- Press Create & Enable, then check your Contacts list in HubSpot.
Filter before you enable
You can filter by event types, properties or any SQL statement, so only the data you care about reaches HubSpot. That's worth doing from day one. A CRM full of anonymous or test profiles is harder to use than one with fewer, better contacts, and my CRM data clean-up guide explains why.
Timing matters too. The person object holds the latest information for the person profile at the time each event is processed. PostHog advises filtering for events on or after property merges, such as an identify call, so the contact HubSpot receives carries the email and name you've attached, not an anonymous ID.
Testing and watching it run
Every destination includes a built-in testing interface that sends real data on demand and helps you debug errors. Use it before you enable: send one known person and check they appear in HubSpot as expected.
Once it's live, the metrics and logs tabs let you monitor usage and inspect errors. There's no limit on how many events you send to a destination, but non-OK HTTP responses are retried up to 3 times, depending on the error code.
Quarantine: why a destination stops by itself
PostHog Docs, on realtime data exports, flag the behaviour that surprises people. A destination must respond with healthy, non-5xx status codes in a timely fashion. One that keeps erroring or responding slowly is quarantined and may eventually be disabled. When that happens, you have to fix the filters or destination and re-enable it by hand. PostHog doesn't count 4xx responses as poor performance.
So if HubSpot contacts stop arriving one day, open the destination's logs first. A disabled destination won't fix itself, and nobody gets a contact until it's switched back on. A 4xx, by contrast, usually points to a problem with the data you're sending, such as a bad field, so check your filters there.
Customising the behaviour
PostHog says the Hubspot destination is open source and maintained by PostHog, with its source code on GitHub. You can view and edit the underlying Hog code of a destination to change what it does. If you'd rather build your own flow, PostHog's webhook destination sends events to any HTTP endpoint with the method, URL parameters and JSON payload you define.
Segment's HubSpot (Classic) destination is another route if you already send data through Segment: it accepts Page, Group, Identify and Track calls and is also open source.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Using the contacts in HubSpot
Once product users land in your Contacts list, put them to work. Build a list of contacts who signed up through the product, or trigger a workflow that welcomes them. My HubSpot workflow recipes include ideas for this, and my guide to using product analytics covers what to track in the first place.
My advice for product-led teams
Filter to identified people before you enable, test with one known profile, and check the logs weekly. If contacts stop flowing, assume quarantine and look at the destination first. Only reach for the Hog code or the webhook destination when the standard destination can't do what you need. For most small SaaS teams, the standard destination with a tight filter is all they'll ever use.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What does the PostHog Hubspot destination send?
PostHog person data, populating your HubSpot Contacts list.
Where do I set it up?
Data pipeline, then Destinations, search Hubspot, + Create.
Can I limit what's sent?
Yes. Filter by event types, properties or SQL.
Can I test before going live?
Yes. Each destination has a built-in testing interface.
What if I need a custom sync?
Use the webhook destination or edit the Hog code.
