Fondoo
GitHubStart your 7-day trial for $0Start trial
Docs

Connect PostHog to Fondoo

Live5 min readUpdated

This connection lets Fondoo and your AI agent read recent product analytics events from one PostHog project. The agent can check what users did on your site or app (page views, sign-ups and other tracked events) in a time window you choose. It is read-only and works with PostHog US Cloud only.

What Fondoo can do with it

The connector id is posthog. It has one capability:

  • events.list (read): lists raw events from your project. It calls GET https://us.posthog.com/api/projects/{projectId}/events/ and passes through three optional inputs: after and before (ISO date-times) and limit (how many events). If you leave out after, PostHog defaults to the last 24 hours.

There are no write actions, so nothing needs owner approval. Agents without the owner scope need the analytics:read scope.

Important limits of this connector:

  • US Cloud only. The address https://us.posthog.com is fixed in the code. EU Cloud (eu.posthog.com) and self-hosted PostHog are not supported by this module. An EU or self-hosted key will fail the connection test.
  • PostHog has deprecated this endpoint. PostHog's API schema says the events list "is effectively deprecated and is kept only for backwards compatibility", and recommends its Query endpoint or batch exports instead. It still works today, but it may change or be removed by PostHog. This may differ for your account.

Before you start

  • A PostHog account on US Cloud (your address bar shows us.posthog.com). PostHog has a free tier; reading data through the API does not add cost. See PostHog pricing.
  • The project you want to read, with events already being captured.
  • Your Fondoo site id, if you want the connection tied to one site.

Step by step: get your credentials

You need two values: a personal API key (secret) and your project id (not secret). The project API key that starts with phc_ is for sending events, not reading them, so it will not work here.

Personal API key

  1. In PostHog, open your account settings and go to Personal API keys (direct link for US Cloud).
  2. Click + Create a personal API Key.
  3. Give it a label, for example Fondoo read.
  4. Limit the key to the organization or project you are connecting, if PostHog offers that choice.
  5. Choose scopes. Tick read access only:
    • Query: Read (query:read). PostHog's API schema lists this as the scope for the events list.
    • Project: Read (project:read). Fondoo's connection test calls GET /api/projects/, which needs project read access. Do not grant write scopes. PostHog recommends picking only the scopes you need (personal API keys). Exact scope labels may differ for your account.
  6. Create the key and copy it straight away. PostHog shows it only once. It normally starts with phx_.
  7. This value goes in the apiKey field.

Project id

  1. Open the project in PostHog. The project id is the number in the address bar after /project/, for example 12345 in us.posthog.com/project/12345/.... You can also look for Project ID in the project settings.
  2. This value goes in the projectId field. It is required.

Connect it in Fondoo

In the dashboard

  1. Go to Connections in the sidebar and click Connect a tool.
  2. In Find a tool, type PostHog.
  3. On the PostHog card, click Use a key. When "Enter your key securely" appears, click Open secure key entry.
  4. On the "Connect posthog" page, fill in apiKey (a hidden password field) and projectId. Click Save connection securely. The page works once and expires after 15 minutes.
  5. The connection shows under Connected with a masked key. Click Check connection.

By asking your agent

Example prompt: "Connect our PostHog project so you can read events. Give me a secure link for the key."

The agent calls:

add_connection_key({ provider: "posthog", siteId: "YOUR-SITE-ID" })

It returns a one-use securePasteUrl (15 minutes). Open it and enter both fields there. Passing the key in fields also works, but Fondoo warns that it may remain in chat logs. connect_service({ provider: "posthog", siteId }) returns the same steps with a signed link and never accepts a key.

REST equivalent:

curl -X POST https://api.getfondoo.com/v1/ops/add_connection_key \
  -H "Authorization: Bearer $FONDOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"posthog","siteId":"YOUR-SITE-ID"}'

Test that it works

  1. Click Check connection, or ask the agent to run test_connection({ connectionId }). Fondoo calls GET https://us.posthog.com/api/projects/ once. A pass shows connected and "Cheap read succeeded; untested permissions remain unknown, not granted." events.list shows as unknown because the test does not check the project id or the query scope.
  2. Ask the agent: "Show me the last 10 PostHog events." It runs:
connector_action({ connectionId, action: "events.list", input: { limit: 10 } })

If events come back, the project id and scopes are right.

Troubleshooting

  • "Connection test failed; check credentials and provider permissions." The key is wrong, revoked, from EU Cloud or self-hosted, or lacks project read. Create a US Cloud personal key with the scopes above and rotate.
  • Test passes but events.list is refused. The key is missing query:read, or it is not allowed to access this project. Edit the key's scopes in PostHog (scopes can be changed later) and try again.
  • "Provider request failed (404)". The projectId is wrong or belongs to another organization. Copy the number from the address bar again and rotate the connection.
  • "Credential fields do not match the connector manifest." Both apiKey and projectId are required, and no other fields are accepted.
  • Empty results. By default PostHog returns only the last 24 hours. Pass a wider after, for example { "after": "2026-10-01T00:00:00Z", "limit": 100 }.
  • Rate limit errors. Wait and retry. See below.

Limits, data and security

  • PostHog limits: most private API rate limits apply per personal API key. PostHog publishes, for example, 240 requests per minute and 1,200 per hour for analytics endpoints, and 480 per minute and 4,800 per hour for other read endpoints. Which bucket the events list falls into may differ for your account. See PostHog API overview.
  • Fondoo limit: a local budget of 60 requests per minute per connection. PostHog's limits and Retry-After stay authoritative.
  • Responses larger than 4 MB are rejected, so keep limit modest.
  • What Fondoo stores: the key and project id, encrypted in Fondoo's connector vault. list_connections shows only masked values. Event results are returned to the caller.
  • Rotate: rotate_connection_key({ connectionId }) returns a new secure paste link and replaces the stored values. You can set expiresAt or rotateAfter to get reminders.
  • Disconnect: delete_connection({ connectionId }) (agents need owner approval). It does not revoke the key in PostHog, so also delete or roll the key under Personal API keys.