PostHog

Install corsair and @corsair-dev/posthog, add the PostHog plugin, and connect with an API key. Then call methods like corsair.posthog.api.events.aliasCreate() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. PostHog requires an API key from your PostHog account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit PostHog, GitHub, Notion, Stripe, and the rest. Trigger PostHog from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for product analytics platform for event tracking, feature flags, session replay, and experiments. Common builds include sync jobs, admin tooling, and agents that call PostHog APIs from your backend. Webhook handlers react to PostHog events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced PostHog records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per PostHog API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/posthog in the open repo. When PostHog ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your PostHog data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store PostHog data on your behalf.