@kapa.ai question about

source-posthog

(v<fill in>, Cloud/OSS) on a multi-organization PostHog account. The source config only takes

api_key

,

start_date

,

base_url

— no org or project field. From what I can tell it discovers projects via the un-nested

GET /api/projects/

, and on PostHog Cloud that endpoint resolves the org from

user.current_organization

— server-side state that changes whenever someone switches org in the PostHog web UI. So my key works, I click a different org in the PostHog UI, and the same unchanged key starts 403ing. Is there a supported way to pin the source to one organization? Or has anyone hit this?

Thinking completed Based on the available documentation and connector configuration for

source-posthog

, there is currently no supported way to pin the connector to a specific organization [PostHog Documentation]. The PostHog connector's configuration schema only accepts the following parameters [PostHog Documentation]: •

api_key

•

start_date

•

base_url

•

events_time_step

Under the hood, all child streams (such as

events

,

cohorts

, and

persons

) dynamically route requests through the IDs returned by the

projects

stream, which fetches records directly from

GET /api/projects/

[manifest.yaml]. Because the connector does not support configuring an organization ID or passing an organization identifier, it relies entirely on whatever context the PostHog API associates with that API key. The knowledge sources do not explicitly document community workarounds for PostHog's UI-driven

current_organization

context switching. In similar scenarios involving multi-tenant/multi-org API keys, standard practice is typically to create a dedicated PostHog service account or user invited exclusively to that single organization, ensuring the key's context cannot be shifted by UI interactions. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.