Connect Strapi to Rig

    Sync your Strapi content into Rig, so your AI tools can reason over what your team publishes alongside the rest of your data. Each content type lands as a table in your warehouse, with its nested components broken out into child tables. Strapi connects with a read-only API token.

    What is Strapi?

    Strapi is an open-source headless CMS. Teams model their own content types, such as articles, products or per-prospect deal rooms, as entries built from reusable components, media and relations, and serve them over a REST API. Because the content lives behind an API rather than in a fixed template, it is a natural source to pull into a warehouse.

    Connecting Strapi to Rig brings that content next to your CRM, billing and product data, so you can tie what you publish to the accounts and revenue it supports, and query the inner detail of each entry in plain English.

    Before you start

    • You need access to the Strapi admin panel with permission to create API Tokens (Super Admin, or a role granted token settings).
    • Know your instance base URL, for example https://your-app.strapiapp.com on Strapi Cloud, or your self-hosted address. No trailing slash and no /api; Rig appends that for you.
    • Rig works with Strapi v4 and v5 through the standard REST API.

    Step 1: Create a read-only API token

    1. In the Strapi admin panel, go to Settings → API Tokens.
    2. Click Create new API Token.
    3. Give it a name like Rig, set Token type to Read-only, and choose a duration (Unlimited is fine for an ongoing sync).
    4. Click Save and copy the token immediately. Strapi only shows it once.

    Read-only is all Rig needs
    Rig only ever reads from Strapi. A read-only token can fetch your entries but cannot create, edit or delete content, so it is safe to hand to the sync.

    Step 2: Connect it in Rig

    1. In Rig, open Connections in the left sidebar and go to the Sources step.
    2. Search for Strapi and click its card.
    3. Paste your instance address into Strapi base URL.
    4. Paste the token into Strapi API token.
    5. Click Continue, then Test to pull a small sample, then Sync to run the full pipeline.

    What Rig pulls in

    Strapi lands in its own strapi schema in your warehouse:

    • Content-type entries: each content type becomes its own table, with scalar fields as columns.
    • Components: nested and repeatable components are normalised into child tables, so the inner content is queryable, not buried in a blob.
    • Relations and media: links between entries and references to media library files come through with each entry.
    • Lifecycle fields: draft and published state, plus created, updated and published timestamps.

    Rig requests each entry with its components populated, so a deeply nested entry arrives as a parent row plus the child tables that make it up.

    Good to know

    • The token reads every content type your API permissions allow. Store it securely and never share it over email or chat.
    • On Strapi v5, Rig keys entries on the stable documentId, so updates merge cleanly across the numeric id changes that happen on publish.
    • Once Strapi content is in your warehouse, you can join it to your CRM and billing sources in Rig to connect what you publish to pipeline and revenue.
    • You can disconnect Strapi at any time from Connections → Sources.

    Was this guide helpful?