Send PostHog event data to Zapier

Last updated:

|Edit this page

Trigger Zaps in Zapier based on PostHog events.

Requirements

Using this requires either PostHog Cloud, or a self-hosted PostHog instance running a recent version of the docker image.

You'll also need access to the relevant Zapier account.

Installation

  1. In PostHog, click the "Data pipeline" tab in the left sidebar.
  2. Click the 'Destinations' tab.
  3. Search for 'Zapier' and select the destination.
  4. Add your Zapier webhook URL at the configuration step.
  5. Press 'Create & Enable' and watch your 'Zaps' get triggered in Zapier!

Configuration

OptionDescription
Zapier hook path
Type: string
Required: True
The path of the Zapier webhook. You can create your own or use our native Zapier integration https://zapier.com/apps/posthog/integrations
JSON Body
Type: json
Required: False
Log responses
Type: boolean
Required: False
Logs the response of http calls for debugging.

FAQ

Is the source code for this destination available?

PostHog is open-source and so are all the destination on the platform. The source code is available on GitHub.

Who maintains this?

This is maintained by PostHog. If you have issues with it not functioning as intended, please let us know!

What if I have feedback on this destination?

We love feature requests and feedback. Please tell us what you think.

What if my question isn't answered above?

We love answering questions. Ask us anything via our community forum.

Questions?

Was this page useful?

Next article

Send PostHog person data to Zendesk

You can also send person properties to User fields in Zendesk. You'll also need access to the relevant Zendesk account. Installation In PostHog, click the " Data pipeline " tab in the left sidebar. Click the 'Destinations' tab. Search for 'Zendesk' and select the destination. Add your Zendesk subdomain, user email, and API token at the configuration step. Press 'Create & Enable' and watch your 'Customer' list get populated in Zendesk! Configuration FAQ Is the source code for this destination…

Read next article