PostHog

About

Forward your PostHog product analytics and error events into Sazabi. PostHog's Data Pipeline posts each matching event to a Sazabi endpoint as a JSON payload, and Sazabi stores it as a log.

PostHog also has a Connect your account path where Sazabi provisions the webhook destination for you. See PostHog account connection page for that setup.

Prerequisites

• A PostHog project with access to CDP / Data Pipeline destinations. This is a paid PostHog feature.
• The PostHog region for your project (US or EU).
• Your Sazabi intake URL (shown above).

Set up in the dashboard

{
  "event": "{event}",
  "person": "{person}"
}

Set up with the CLI

You can also register the PostHog log source with the Sazabi CLI (installed and authenticated — see CLI reference).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

sazabi log-sources create posthog --mode connectionless

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.

Verify

Send a test event from the PostHog destination form. Open the Intake page in the Sazabi dashboard and confirm events from the PostHog source appear. Records typically arrive within a minute or two of the test event.

Troubleshooting

Test event delivery fails — Confirm you pasted the full Sazabi intake URL including https://. Check PostHog's delivery logs for the destination to see the HTTP response code.

No events after saving — PostHog delivers events only when they match the destination's filter criteria. If the destination has no filter, all captured events are forwarded; if a filter is configured, verify it matches events in your recent activity.

Further reading