PostHog Webhook Setup Guide

The Native Webhook URL is available on the Link Account form or by editing the linked account in the StackOne Hub.

• Copy the full URL and keep it ready for the next step

In PostHog, navigate to Data > Pipelines > Destinations > + New Destination > search HTTP Webhook > + Create.

Configure the destination with the following settings.

• Paste the Native Webhook URL into the Webhook URL field
• Method: POST (default)
• In Headers, click + Add entry and set key x-posthog-project-token with your Project Token value (format: phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
• Keep the default JSON Body: {“event”: “{event}”, “person”: “{person}”} — do not modify this

Add filters to control which events are sent. Without filters, PostHog sends all events.

• In Filters, click Add filter or Match event
• Add event names to forward: $identify</code>, <code>$pageview, $feature_flag_called</code>, <code>$exception, or custom events like user_signed_up. Check next step to create custom events in PostHog.
• To send all events, leave filters empty

Custom events are created automatically in PostHog when first captured. You can create them using StackOne’s capture_event action or the PostHog SDK.

• Use StackOne’s capture_event action to send a custom event to PostHog — the event will be auto-created on first capture
• Add the exact event name to your webhook filter — names are case-sensitive (e.g., user_signed_up and User_Signed_Up are treated as different events)

Click Create & Enable to activate. To test, use the Testing section in the destination page.

• If test shows “Destination was skipped”, this means the sample event didn’t match your filters. You can temporarily remove the applied filters to test connectivity, then re-add them.
• Check the Logs tab for 200 OK responses

PostHog system events are prefixed with $</code>. To find and add them in your webhook destination, go to the <strong>Filters</strong> section, click <strong>Add filter</strong>, and type <code>$ to search available system events by name.

• $pageview</code> — Page view (web)</li> <li><code>$pageleave — Page leave (web)
• $screen</code> — Screen view (mobile)</li> <li><code>$identify — User identified
• $set</code> — Person properties set</li> <li><code>$feature_flag_called — Feature flag evaluated
• $autocapture</code> — Auto-captured interaction</li> <li><code>$group — Group event
• $groupidentify</code> — Group identified</li> <li><code>$exception — Error tracked

Any non-system event is handled by the catch-all handler. The original event name is preserved.

Check the following common problems and their solutions.

• No events: Verify destination is enabled under Status widget in destination configuration page.
• 404: Native Webhook URL is incorrect — re-copy from StackOne Hub
• 401/403: Linked account may not be fully configured
• Events filtered out: Check filter list includes expected events
• Wrong payload: Reset JSON body to default {“event”: “{event}”, “person”: “{person}“}