The Scenario
The handoff note from the engineer who built your company's Make administration tool said: "Column validation uses a local enum list — check it against the API before submitting anything, the local list is probably stale."
That was six months ago. You inherited the tool last week. The provisioning checklist in the Excel workbook has dropdowns for module types and variable types, and you have no idea if they still match what Make's API accepts. An audit request came in from the compliance team this morning — they want documentation of all valid input values used in the administration tool.
The bad version:
- Find the Make API reference for module types, call the endpoint, copy the response values into a worksheet in the workbook
- Repeat for variable types, organization features, and user features — four separate API calls, four separate copy-paste sessions
- Realize the module types list has changed since the local enum was built and spend time reconciling the differences
Compliance needs this documented by end of week. Reconciling stale local lists one by one is not going to get you there.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Excel workbook. It connects to Make's API and can fetch all enumeration types at once, routing each to a labeled worksheet.
In the administration workbook, run:
Pull Make's available module types and variable types into columns A and B of separate Excel sheets so I can reference them as allowed values in a provisioning checklist
Or for all four at once:
Fetch all Make enumerations — module types, variable types, organization features, and user features — and write each list to a separate worksheet in this workbook labeled with the enum type
What You Get
- A "Module Types" worksheet with every valid module type value Make accepts
- A "Variable Types" worksheet with the full list of valid variable types
- An "Organization Features" worksheet and a "User Features" worksheet with all valid feature flags
- Each worksheet is labeled and immediately usable for reconciliation against the local enum list in the provisioning checklist
What If the Data Is Not Quite Ready
What if I want to compare Make's values against my existing local list in column A?
Fetch all Make module types and write them into column B of the "Module Types" worksheet — I have my local enum list in column A and want to compare the two side by side
What if I want a diff column showing which local values are missing from the API response?
Fetch all Make module types into column B of the "Module Types" worksheet, then add a formula in column C that marks each row in column A as "Valid" if the value exists in column B or "Missing from API" if it does not
What if I only need module types and variable types for the immediate audit?
Fetch Make's available module types and variable types and write each to a separate worksheet named "Module Types" and "Variable Types"
What if I need all four enumerations fetched, each on its own worksheet, plus a summary worksheet listing the count of values per enum type and any discrepancy count versus the local lists already in the workbook?
Fetch all Make enumerations — module types, variable types, organization features, and user features — write each to a labeled worksheet, then create a "Summary" worksheet showing the enum name, the count of API values, and the count of local values so I can spot where the lists have drifted
The pattern: ask for the pull and the reconciliation logic together, so the compliance documentation comes out ready rather than requiring a manual diff afterward.
Try It
Get the 7-day free trial of SheetXAI and open the administration workbook in Excel, then ask it to fetch your Make enum reference tables. Also useful: exporting the LLM model catalog for AI scenario planning, or pulling valid region and timezone values for provisioning forms — both covered in the Make integration overview.