Send PostHog event data to Knock

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

Installation

In PostHog, click the Data pipeline tab in the left sidebar.
Click the Destinations tab.
Search for Knock and click + Create.
Add your Knock.app webhook destination URL at the configuration step.
Press Create & Enable and watch your 'Audience' list get populated in Knock!

Option	Description
`Knock.app webhook destination URL` Type: string Required: True
`User ID` Type: string Required: True	The identifier for the user in Knock. The default sends the PostHog distinct ID, which matches the identifier your app already uses. It sends nothing for an anonymous event, where the distinct ID is still the device ID, and nothing for an event with no person, so you do not get Knock recipients you cannot notify. Set this to another value, such as an `email` or your own `id`, if your Knock users use a different identifier. Do not use the PostHog person ID (`{person.id}`): it is a PostHog-owned UUID that Knock has never seen, so it creates a second Knock user record. If the value is empty, nothing is sent. See here for more information: https://docs.knock.app/concepts/users#user-identifiers
`Include all properties as attributes` Type: boolean Required: True	If set, all event properties will be included as attributes. Individual attributes can be overridden below.
`Attribute mapping` Type: dictionary Required: False	Map of Knock.app attributes and their values. You can use the filters section to filter out unwanted events.

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

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