Connect Strapi to Rig

    Sync deal room entries from your Strapi instance into Rig, so your AI tools can reason over them alongside the rest of your data. The connector reads one content type, deal rooms, and lands its published entries as a table in your warehouse, with repeatable components and dynamic zones 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. Leave off the trailing slash and /api; Rig appends that for you.
    • Rig works with Strapi v4 and v5 through the standard REST API.
    • Rig reads one content type: the one whose plural API ID is deal-rooms, served at /api/deal-rooms. Other content types are not synced. On an instance without that content type, Continue shows No streams reachable, with deal_rooms marked Endpoint not found.

    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

    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 Strapi, open the card and click Connect.
    3. Paste your instance address into Strapi base URL.
    4. Paste the token into Strapi API token.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. 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

    Strapi lands in its own strapi schema in your warehouse:

    • Deal rooms: one row per published deal room entry, with its scalar fields as columns. Drafts are not synced.
    • Components: a single component on the entry is flattened into columns on the deal room's row. Repeatable components and dynamic zones become child tables, so you can query their content directly.
    • Relations and media: links between entries and references to media library files come through with each entry.
    • Lifecycle fields: created, updated and published timestamps.

    Rig asks Strapi to populate each entry one level deep. Components, relations and media directly on a deal room come through, but anything nested inside them is not fetched.

    Good to know

    • The token can read every content type your API permissions allow, even though Rig only requests deal rooms. 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.
    • To disconnect Strapi, 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

    • Query CMS content alongside the rest of your data
    • Audit publishing activity and content freshness
    • Connect content to accounts and revenue
    • Reason over nested components in plain English

    More ideas for using Strapi

    Was this guide helpful?