Strapi integration for Rig
The easiest way to connect Strapi to Claude and other AI tools
Strapi is an open-source headless CMS where teams model content types (articles, products, deal rooms and more) as entries with reusable components, media and relations, served over a REST API.
What Rig syncs from Strapi
Once connected, Rig models these objects so questions resolve to the right tables and joins:
- Deal room entries
- Components
- Dynamic zones
- Relations
- Media references
- Published entries only
- Created, updated and published timestamps
How Strapi connects to Rig
Rig Ingest syncs the deal-rooms content type from your Strapi instance into your warehouse on a schedule, using a read-only API token. Published entries land as one table, and repeatable components and dynamic zones on each entry are normalised into child tables. Other content types and drafts are not synced.
Read the step-by-step Strapi setup guideQuery CMS content alongside the rest of your data
Rig lands your Strapi deal rooms as a table in your warehouse, so the collateral your team publishes sits next to your CRM, billing and product data. You can ask about what's published, when it changed and how it maps to accounts without exporting anything from the CMS.
- How many deal rooms were published this month?
- Which entries changed in the last week?
- List published deal rooms and the company each is for
Audit publishing activity and content freshness
Strapi tracks created, updated and published timestamps per entry. Rig reads them for every published entry, so you can measure how fresh your content is and find entries that have gone stale.
- Which deal rooms were updated this week?
- Show entries not updated in over 90 days
- What is the average time from create to publish?
Connect content to accounts and revenue
When a content type carries a company or account field, like a per-prospect deal room, Rig joins it to your CRM and billing data. That ties the collateral your team ships to the pipeline and revenue it supports.
- Which deal rooms map to open opportunities?
- Show accounts with a published deal room and their stage
- Which prospects have a deal room but no recent activity?
Reason over nested components in plain English
Strapi entries are built from reusable components. Rig asks Strapi to populate each entry one level deep and normalises repeatable components and dynamic zones into child tables, so an AI assistant can answer questions about sections, line items or action plans as well as the top-level entry. Anything nested deeper than that is not fetched.
- List the mutual action plan steps across all deal rooms
- What commercial offer items appear most often?
- Show the product features highlighted in each entry
Ask your Strapi data in Claude, ChatGPT or Cursor
Rig serves your Strapi data to AI assistants over MCP. Once Strapi is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL.
Frequently asked questions
- What Strapi data does Rig sync?
- Published entries of the deal-rooms content type, with the components, dynamic zones, relations and media references on each entry populated one level deep, plus create, update and publish timestamps. Drafts and other content types are not synced.
- Does Rig work with Strapi v4 and v5?
- Yes. The connector uses Strapi's REST API with page-based pagination and a read-only API token, and keys on the stable documentId where v5 exposes it.
- Can I query Strapi content in Claude or ChatGPT?
- Yes. Once Strapi is synced to your warehouse, Rig serves it to Claude, ChatGPT, Cursor and other AI tools over MCP.
- How often does Strapi data refresh?
- Rig Ingest syncs on a schedule you set and tracks schema changes automatically, so new fields on deal rooms appear without extra setup.
Connect Strapi data to AI tools like Claude
Rig builds a governed context layer over your data so every team, and every AI tool, asks questions and gets answers they can trust.