You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a specific format for "capture" to ingest data. This generally works fine for people directly integrating with us but a lot of people want to use a platform's webhook to trigger ingestion to us. To do this they often need to use a 3rd party such as Zapier to transform the data into the appropriate format before coming to us.
Describe the solution you'd like
Now that we have custom hog functions, we could potentially offer a custom webhook experience where you created a Webhook source which can then be hit at something like us.posthog.com/incoming_webhooks/:id. This would likely just immediately respond 200 and queue the payload for later processing which would then use the user's implemented hog code to transform it into the relevant event payload.
The text was updated successfully, but these errors were encountered:
Feature request
Is your feature request related to a problem?
We have a specific format for "capture" to ingest data. This generally works fine for people directly integrating with us but a lot of people want to use a platform's webhook to trigger ingestion to us. To do this they often need to use a 3rd party such as Zapier to transform the data into the appropriate format before coming to us.
Describe the solution you'd like
Now that we have custom hog functions, we could potentially offer a custom webhook experience where you created a Webhook source which can then be hit at something like
us.posthog.com/incoming_webhooks/:id
. This would likely just immediately respond 200 and queue the payload for later processing which would then use the user's implemented hog code to transform it into the relevant event payload.The text was updated successfully, but these errors were encountered: