The Scenario
An internal compliance audit requires a 90-day change log for five critical Metabase dashboards. The auditor wants to know who changed what, and when, for each dashboard. Metabase stores revision history, but the only way to see it natively is to click "History" inside each dashboard and read through a chronological list one entry at a time — no export button, no date filter, no way to get the data into a format the auditor can actually work with.
The bad version:
- Open each of the five dashboards in Metabase, click the History button, and start scrolling through the revision log.
- Copy each revision's timestamp, user name, and change description into a Google Sheet manually, one row at a time.
- Realize that Metabase's revision descriptions are sometimes vague ("Updated dashboard") and sometimes specific ("Changed filter for date range"), so the change log you're producing requires you to make editorial judgments about which revisions are audit-relevant.
- Finish three of the five dashboards before the end of the day and stitch together an incomplete log that will require a follow-up.
A 90-day log for five dashboards sounds like a small task. It's not, when the only tool you have is a scroll and a copy.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It can pull the full revision history for Metabase dashboards and write each revision — timestamp, user, change description — into the sheet, sorted and ready for the auditor.
Fetch the revision history for Metabase dashboard ID 22 and write each revision's timestamp, user name, and change description into this sheet sorted from newest to oldest
What You Get
- One row per revision: timestamp, user name, change description as Metabase recorded it.
- Sorted newest to oldest — the most recent changes are at the top.
- If a revision has no description (Metabase sometimes records these as blank), the cell is blank rather than missing — the row is still present.
What If the Data Is Not Quite Ready
You need revision history for all five dashboards in one pass
For each dashboard ID in column A of this sheet, pull the full revision history from Metabase and write editor name, date, and change summary into a new tab named after the dashboard ID
One prompt, five tabs, complete change logs for all five dashboards. The auditor gets the full picture without five separate prompts.
You need to filter for revisions within a specific 90-day window
Fetch the revision history for Metabase dashboard ID 22 and write timestamp, user, and change description into this sheet — include only revisions where the timestamp falls between 2026-02-13 and 2026-05-14, sorted newest to oldest
The 90-day window is applied before the data lands in the sheet. The auditor gets only the relevant period.
You want to flag revisions made outside business hours
Fetch the revision history for Metabase dashboard ID 22, write timestamp, user, and change description into this sheet, and in column D write AFTER HOURS for any revision where the timestamp is outside 9 AM to 6 PM local time
Compliance teams sometimes flag late-night changes to production dashboards. The AFTER HOURS column surfaces them without manual timestamp review.
Full five-dashboard audit package in one shot
For each dashboard ID in column A of this sheet, fetch the revision history from Metabase and write it into a tab named after the dashboard ID. Filter to revisions between 2026-02-13 and 2026-05-14. Include timestamp, user, and change description. In a Summary tab, write one row per dashboard with dashboard ID, total revisions in the window, and the name of the user who made the most changes.
One prompt, five tabs plus a summary, 90-day scoped, with the most active editor identified per dashboard. The audit package is complete.
Try It
Get the 7-day free trial of SheetXAI and open the Google Sheet for your compliance audit, then ask it to pull the revision history for your critical Metabase dashboards. Also useful: auditing your Metabase workspace inventory, and the hub overview on connecting Metabase to Google Sheets.