> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking ConfigCat as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/configcat

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The ConfigCat connector syncs your feature-flag account structure into the PostHog data warehouse, including your organizations and products.

## Prerequisites

You need a ConfigCat account with **Public Management API credentials**. These are a username and password pair — separate from your SDK keys — that grant read access to your account data through the [ConfigCat Public Management API](https://api.configcat.com/docs).

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking ConfigCat, you'll need:

-   **Public API username** – the username from your Public Management API credential.
-   **Public API password** – the password from your Public Management API credential.

Create these under **Public Management API credentials** in your [ConfigCat dashboard](https://app.configcat.com/my-account/public-api-credentials).

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `products` | The top-level container that groups configs, environments, and feature flags | Full refresh |
| `organizations` | The account-level owner of products and members | Full refresh |

All tables use **full refresh** syncing — the entire table is reloaded on each sync. Incremental sync is not available because the ConfigCat API does not expose pagination or server-side timestamp filters.

> **Note:** Deeper resources like configs, environments, settings, and feature flag values are not included in this initial release. Only top-level products and organizations are synced.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Public API username` | password | Yes |
| `Public API password` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `products` | A ConfigCat product — the top-level container that groups configs, environments, and feature flags. | Full refresh | — | — |
| `organizations` | A ConfigCat organization — the account-level owner of products and members. | Full refresh | — | — |
| `configs` | A ConfigCat config — the container within a product that groups feature flags and settings. | Full refresh | — | — |
| `environments` | A ConfigCat environment — a deployment target such as production or staging, which each feature flag holds its own value in. | Full refresh | — | — |
| `settings` | A ConfigCat feature flag or setting — the definition of the flag itself, without its per-environment values. | Full refresh | — | — |
| `setting_values` | The value a ConfigCat feature flag or setting evaluates to in one environment, with its targeting rules — one row per flag per environment. | Full refresh | — | — |
| `audit_logs` | A ConfigCat audit log entry — one recorded change to a product, config, environment, feature flag or member, with who made it and why. | Incremental, Full refresh | auditLogDateTime | — |
| `organization_members` | A person's membership of a ConfigCat organization — one row per user per role, so a user who is both an admin and a billing manager appears twice. | Full refresh | — | — |
| `product_members` | A person's access to a ConfigCat product, with the permission group that decides what they can change. | Full refresh | — | — |
| `stale_flags` | A ConfigCat zombie (stale) flag — a feature flag nothing has changed for long enough that it is a candidate for removal, with its staleness in each environment. | Full refresh | — | — |
| `tags` | A ConfigCat tag — a label attached to feature flags to group them, defined per product. | Full refresh | — | — |
| `tag_settings` | The tag to feature flag junction — one row per feature flag carrying a tag, with the flag's own details. | Full refresh | — | — |

## Troubleshooting

-   If you see an **authentication error** (401), your Public API credentials are invalid or have been revoked. Generate a new credential in your [ConfigCat dashboard](https://app.configcat.com/my-account/public-api-credentials), then reconnect.
-   If you see a **permissions error** (403), your Public API credentials do not have access to this data. Check the credential's permissions, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.