> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Circle as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/circle-so > **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) - [API quota](#api-quota) - [Sync modes](#sync-modes) - [Configuration](#configuration) - [Supported tables](#supported-tables) - [Troubleshooting](#troubleshooting) ![](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 Circle connector syncs your community data – members, spaces, posts, comments, events, courses, and payments – into PostHog, so you can analyze community engagement alongside your product data. ## Prerequisites You need a Circle account on the **Business** plan or above. The Admin API is only available on Business and higher-tier plans. You'll also need an Admin V2 API token. Create one by going to **Settings > Developers > Tokens** in Circle and selecting the **Admin V2** token type. ## 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 Circle, you'll need: - **Admin API token** – your Admin V2 API token created in Circle's developer settings. ## API quota Every request counts toward your Circle plan's monthly Admin API quota (5,000 requests on the Business plan). Each request reads up to 100 records. Some tables sync per parent record – `space_members` makes one request per space, `space_group_members` makes one request per space group, `event_attendees` makes one request per event, and `form_submissions` makes one request per form. Sync only the tables you need to conserve your quota. ## Sync modes Each table can be synced in one of several modes, depending on what the source supports: - **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes. - **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured. - **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs. - **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected. See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them. **Note:** All Circle tables sync using full refresh only. Circle's API does not support filtering by update time for most resources, and charge records can be modified by refunds without changing their creation timestamp, so incremental sync would miss these updates. ## Configuration | Option | Type | Required | | --- | --- | --- | | `Admin API token` | password | Yes | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `community_members` | A member of the community. | Full refresh | — | — | | `member_tags` | A tag that can be assigned to community members. | Full refresh | — | — | | `tagged_members` | An assignment of a member tag to a community member. | Full refresh | — | — | | `spaces` | A space in the community, such as a post feed, course, event list or chat room. | Full refresh | — | — | | `space_members` | A member of a space. | Full refresh | — | — | | `space_groups` | A group that organizes spaces in the community. | Full refresh | — | — | | `space_group_members` | A member of a space group. | Full refresh | — | — | | `posts` | A post in a space, in any status. | Full refresh | — | — | | `comments` | A comment on a post. | Full refresh | — | — | | `topics` | A topic used to categorize posts. | Full refresh | — | — | | `events` | A published event in the community. | Full refresh | — | — | | `event_attendees` | A member who RSVPed yes to an event. | Full refresh | — | — | | `course_sections` | A section of a course space. | Full refresh | — | — | | `course_lessons` | A lesson in a course section. | Full refresh | — | — | | `access_groups` | A group that controls member access to spaces. | Full refresh | — | — | | `invitation_links` | A link that invites people to join the community. | Full refresh | — | — | | `community_segments` | A saved segment of community members. | Full refresh | — | — | | `forms` | A form in the community. | Full refresh | — | — | | `form_submissions` | A submission to a form. | Full refresh | — | — | | `paywalls` | A paywall and its prices. | Full refresh | — | — | | `community_member_subscriptions` | A paid subscription of a community member. | Full refresh | — | — | | `community_member_charges` | A payment charge of a community member. | Full refresh | — | — | ## Troubleshooting 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.