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:
- Content-type entries
- Components and nested components
- Dynamic zones
- Relations
- Media library files
- Draft and published states
- Created and updated timestamps
How Strapi connects to Rig
Rig Ingest syncs your Strapi entries into your warehouse on a schedule using a read-only API token. Each content type becomes a table and its nested components are normalised into child tables, so content questions resolve correctly.
Query CMS content alongside the rest of your data
Rig lands each Strapi content type as a table in your warehouse, so the copy 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 entries were published in each content type 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 and a draft/published state per entry. Rig reads them, so you can measure how fresh your content is and find entries that are stale or stuck in draft.
- Which entries are still in draft?
- 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, often several levels deep. Rig normalises that nested tree into child tables, so an AI assistant can answer questions about the inner content, like sections, line items or action plans, not just the top-level entry.
- 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?
- Content-type entries with their components, nested components, dynamic zones, relations and media references, plus draft/published state and create, update and publish timestamps.
- 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 content types and fields 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.