--- title: "Make Integration for Rig: Query Make Data in Plain English" description: "Connect Make to Rig and query your Make data in plain English, or ask it in Claude, ChatGPT and Cursor. Governed, validated answers from your warehouse." canonical: "https://rig.so/integrations/make" format: markdown --- Browse integrations ![Make logo](https://img.logo.dev/make.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=112&format=png&retina=true) People & operations Supported # Make integration for Rig ## The easiest way to connect Make to Claude and other AI tools Make is a visual automation platform where teams build scenarios that move data between apps through chains of modules. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) ## What Rig syncs from Make Once connected, Rig models these objects so questions resolve to the right tables and joins: - Organizations - Teams - Scenarios - Scenario execution logs - Scenario notes - Scenario blueprints with module field mappings ## How Make connects to Rig Rig Ingest syncs your Make organisations, teams, scenarios, logs, notes and blueprints into your warehouse on a schedule, using a read-only API token for your Make zone. The blueprints carry every module's field mappings, so Rig can search them like any other table. [Read the step-by-step Make setup guide](https://rig.so/guides/connect-make) ## Trace which scenarios read or write a field Field lineage in Make is the set of scenarios whose modules map a given field, either as an input or as an output. Rig reads each scenario's blueprint with its module field mappings, so before you rename or remove a field in another system you can list every scenario that depends on it. Ask Rig - Which Make scenarios map the field lifecycle\_stage? - List every scenario that writes to our CRM, with its team - Which scenarios would a rename of the customer\_id field affect? ## Inventory your automations by team An automation inventory lists which scenarios exist, who owns them and which team they sit in. Rig joins organisations, teams and scenarios, so you can see how automation is spread across the company and spot teams with a lot of scenarios nobody has documented. Ask Rig - Count scenarios per team - Which scenarios have no notes attached? - List all scenarios in the marketing team ## Review scenario run history Execution logs record how a scenario ran each time it was triggered. Rig syncs those logs next to the scenario they belong to, so you can find the scenarios that run most often and look at how a particular one has behaved over time, in the same place as the rest of your data. Ask Rig - Which scenarios have the most executions in the logs? - Show the recent execution history for one scenario - Rank teams by how often their scenarios appear in the logs ## Ask your Make data in Claude, ChatGPT or Cursor Rig serves your Make data to AI assistants over MCP. Once Make 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. - [Claude](https://rig.so/integrations/claude) - [Claude Code](https://rig.so/integrations/claude-code) - [Cursor](https://rig.so/integrations/cursor) - [ChatGPT](https://rig.so/integrations/chatgpt) - [Codex](https://rig.so/integrations/codex) - [Gemini](https://rig.so/integrations/gemini) ## Frequently asked questions What Make data does Rig sync? Organisations, teams, scenarios, each scenario's execution logs and notes, and each scenario's blueprint with the field mappings of every module. What does the Make API token need to do? Read only. Rig asks for the organizations:read, teams:read and scenarios:read scopes and cannot change anything in Make. Does Rig cover more than one Make zone? Each zone needs its own token, because Make issues tokens per zone. Connect each zone as its own source, using its regional URL such as eu1.make.com or us1.make.com. Can I query Make data in Claude or ChatGPT? Yes. Once Make is synced to your warehouse, Rig serves it to Claude, ChatGPT, Cursor and other AI tools over MCP. ## Related integrations [![CharlieHR logo](https://img.logo.dev/charliehr.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)CharlieHRPeople, teams and leave from CharlieHR, with salary data never synced.](https://rig.so/integrations/charliehr)[![Google Workspace Directory logo](https://img.logo.dev/workspace.google.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Google Workspace DirectoryAccounts, managers, departments and org units from Google Workspace.](https://rig.so/integrations/google-workspace-directory)[![Greenhouse logo](https://img.logo.dev/greenhouse.io?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)GreenhouseCandidates, applications, interviews and offers from Greenhouse Harvest.](https://rig.so/integrations/greenhouse)[![Rippling logo](https://img.logo.dev/rippling.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)RipplingWorkers, org structure, leave, time and recruiting data from Rippling.](https://rig.so/integrations/rippling)[![SCORM Cloud logo](https://img.logo.dev/scorm.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)SCORM CloudCourses and learner registrations from SCORM Cloud.](https://rig.so/integrations/scorm-cloud)[![Sumsub logo](https://img.logo.dev/sumsub.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)SumsubKYC and KYB applicant status, data-minimised by design.](https://rig.so/integrations/sumsub) ## Connect Make 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. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) --- - [This page as HTML](https://rig.so/integrations/make) - [Site map for language models](https://rig.so/llms.txt) - [API and agent documentation](https://rig.so/developers)