There are two routes. The recommended one: in Zapier, create a Zap and add the PostHog app as the trigger, which only receives events from actions. The alternative: in PostHog, open Data pipelines, Destinations, create a Zapier destination and point it at a Zap with a webhook trigger. Zapier's Capture Event action sends events the other way.
PostHog's docs describe the Zapier connection as a way to trigger Zaps from PostHog events. That opens up a lot: a trial sign-up that creates a CRM contact, a feature used for the first time that adds someone to an email sequence, or a cancelled subscription that alerts the account manager.
Which route to pick
| Route | Starts in | Good for |
|---|---|---|
| PostHog app as a Zap trigger (recommended) | Zapier | Triggering on a PostHog action you've defined |
| Zapier destination in Data pipelines | PostHog | Sending events to a Zap through a webhook |
| Capture Event action | Zapier | Sending events from other apps into PostHog |
Before you start, you'll need PostHog Cloud or a self-hosted PostHog running a recent version of the docker image, plus access to the Zapier account.
Route one: the PostHog app in Zapier
- In Zapier, create a new Zap.
- Add the PostHog app as the trigger and choose Action Performed, filling in your Organization, Project and Action.
- If there's no PostHog action yet for the event you care about, create one in PostHog first.
Zapier lists Action Performed as firing when a user performs an action, and it starts the Zap instantly.
Route two: the Zapier destination
- In PostHog, click Data pipeline in the sidebar, open the Destinations tab, search for Zapier and click + Create.
- In Zapier, create a Zap with a webhook trigger and copy its URL.
- Paste the URL into PostHog under Zapier hook path.
- Press Create & Enable and watch your Zaps trigger.
PostHog says it's open source, destinations included, and this destination is maintained by PostHog.
Events need to be actions first
Here's the rule that explains most 'it isn't triggering' problems. PostHog Docs note that the PostHog app in Zapier only supports receiving events from actions, not raw events. An action in PostHog is a named definition built from one or more events, such as 'Clicked upgrade button'. If you haven't created an action for the event you want, the app has nothing to listen for, so define it first.
The same docs remind you that the Zapier destination needs PostHog Cloud or a recent self-hosted image. On an older self-hosted install, update before you try route two.
Sending data back into PostHog
Zapier also lists a Capture Event action. It needs your Organization, Project, an Event Name and the user's PostHog Distinct ID, with optional Event Properties and a Timestamp. That's how you'd log events that happen outside your product, and it's what turns PostHog into a fuller record of each customer, say a sales call booked in a calendar tool or an invoice settled in accounting software, against the same person in PostHog.
The Distinct ID is the piece to get right. If the other app doesn't know the user's PostHog ID, store it somewhere it can be looked up, such as a CRM field, so the event lands on the right person.
Other ways to move PostHog data
PostHog's destination list also includes Make, Webhook, Slack, HubSpot, Intercom, Klaviyo, Sendgrid and Zendesk, among others, so you may not need Zapier at all for a common tool. n8n has a built-in PostHog node that can create aliases, events and identities, and track pages. If you're weighing the automation tools, my n8n and Zapier comparison sets out the differences, and this guide to using product analytics helps you pick which actions are worth automating.
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.
My advice for your first Zap
Pick one action that someone should hear about straight away, define it in PostHog, and use the PostHog app trigger in Zapier. Test it with your own account first, and check the Zap history to confirm the trigger fired once, not twice. Check the destination list before you build a Zap for a common tool, because a direct destination has fewer moving parts. If it all gets too much, here's how to hire an automation expert.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Can PostHog trigger a Zap?
Yes, through the PostHog app in Zapier or the Zapier destination in Data pipelines.
Can Zapier send events to PostHog?
Yes. Zapier lists a Capture Event action for that.
Why isn't my event triggering?
The PostHog app only receives events from actions, so create an action for the event.
Does it work self-hosted?
Yes, with a recent version of the docker image.
Are there alternatives to Zapier?
PostHog's destination list includes Make and Webhook, and n8n has a PostHog node.
