Connect Thinkific to Rig

    Sync your Thinkific site into Rig, from courses, chapters and contents to students, groups, enrolments and orders. The connection uses an API access token created in your site settings.

    Before you start

    • You need to be an admin of the Thinkific site.
    • Your Thinkific plan must include API access. A 401 on connect can mean the plan does not.

    Step 1: Create an API access token

    1. In Thinkific, go to Settings and open the Code & analytics tab.
    2. Choose API Access Tokens from the menu on the left.
    3. Click Add API access token and give it a name.
    4. Copy the token and note its expiry date. Thinkific shows the token once.

    Rotate before it expires
    The token carries an expiry date. Create a new one and update the connection in Rig before that date, or syncs will start failing.

    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 Thinkific, open the card and click Connect.
    3. API access token: Paste the token you copied. The token belongs to one site, so you do not enter a subdomain.
    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 nightly 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

    Thinkific lands in its own thinkific schema in your warehouse:

    • Content: courses, chapters, contents, bundles, products, collections and the collection to product links.
    • People: users with their roles, instructors, groups and group memberships.
    • Enrolments: course enrolments and bundle enrolments.
    • Orders: orders with their line items.

    Good to know

    • Every table is re-read in full on each sync, because the API has no deletion log. A row removed in Thinkific stays in your warehouse with _rig_deleted set to true.
    • Thinkific's older API key and subdomain scheme is separate, and Rig uses the access token.
    • Bundles have no list endpoint in Thinkific, so Rig finds them through your products.
    • To disconnect Thinkific, 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 course sales
    • Follow student enrolment
    • Review course content
    • Manage groups of learners

    More ideas for using Thinkific

    Was this guide helpful?