Connect Circle to Rig

    Sync your Circle community into Rig: members and their tags, spaces, posts, comments, events and event RSVPs. Circle connects with an Admin V2 API token, which needs the Business plan or above.

    Before you start

    • You need to be a community admin in Circle.
    • The Admin API needs the Business plan or above. On a lower plan, Circle answers every call with a 403 and the connection fails.
    • Circle counts Admin API calls per month: 5,000 on Business. Every sync spends part of that quota, and your own automations share it. Rig syncs a new Circle connection monthly, on the 1st, for that reason.

    Step 1: Create a Circle Admin V2 token

    1. In Circle, go to Settings then Developers then Tokens.
    2. Click Create token and choose the type Admin V2.
    3. Name it, such as Rig, and create it.
    4. Copy the token. It identifies your community, so no community ID or URL is needed.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Circle, open the card and click Connect.
    3. Admin API token: paste the Admin V2 token.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. The source then syncs on its schedule, which is monthly, on the 1st unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Circle lands in its own circle schema in your warehouse:

    • Members: community members with last-seen time and profile fields.
    • Member tags: the tag list. The link between members and tags (tagged_members) is off by default.
    • Spaces: your spaces.
    • Posts and comments: every post and comment across the community.
    • Events and RSVPs: events and the RSVPs loaded with each event.

    Every sync re-reads each stream in full. A run costs about one API call per 100 rows, plus one call per event.

    Good to know

    • A new connection syncs monthly at 00:00 UTC on the 1st. Sync more often only if you know your plan's quota can take it.
    • An HTTP 429 on every stream usually means the month's quota is spent. It resets next month, and it also blocks your own Circle automations until then.
    • Event data holds RSVPs only. Check-ins are not pulled, and a withdrawn RSVP is not removed, so count the RSVPs from the latest sync and check that sync was not partial.
    • Because the member read takes a while, last_seen_at is a snapshot. A member who visits during the run can show the new month.
    • To disconnect Circle, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Measure community membership and activity
    • See which spaces and posts drive discussion
    • Track event attendance

    More ideas for using Circle

    Circle documentation

    Was this guide helpful?