How to Connect Metabase to Google Sheets (4 Methods Compared)

The Problem With Getting Sheet Data In and Out of Metabase

You have a Google Sheet full of data — subscription metrics, cohort breakdowns, campaign spend — and you need it either fed into Metabase or pulled back out from a query result. The default flow is anything but smooth: you run the query in Metabase, download the CSV, open it locally, clean up the column headers, and paste the rows into the sheet. Then the query gets updated, and you do it again.

Metabase is good at letting non-engineers run SQL and saved questions against production databases without touching the database directly. But the gap between "Metabase has the answer" and "my spreadsheet has the answer" is still manual by default. Below are the four ways teams typically close that gap.

Method 1: Manual Copy-Paste

The baseline. You run your query or open your dashboard in Metabase, click the download button, grab the CSV, and import it into your Google Sheet by hand.

For a one-time pull — say, exporting 200 rows of subscription data for a contract negotiation — this works fine. You do it once and you're done.

The grind shows up the third or fourth time you need the same data. The export file lands with underscore-separated column names that don't match your sheet headers. You rename them. The next week, someone changes the query and adds two columns, which means your paste range is off by two. You fix it. Then leadership asks for the report weekly, and suddenly you're spending 40 minutes every Monday morning doing a job that doesn't appear anywhere in your job description.

Method 2: Zapier or Make

Both platforms have Metabase connectors. You can set up a trigger — a schedule, a webhook, a sheet change — and have it call the Metabase API to run a saved question and write the result back to your sheet.

Before you go further: do you know what a dataset query payload looks like in Metabase's API? Do you know how to map the JSON column array to specific sheet columns? Do you know what a session token is and how to refresh it? If those questions landed with a thud, skip ahead to Method 3 or 4. This path is built for people who configure automations for a living.

If you're still here: the flow works. You pick the trigger, write the Metabase API call, parse the response, and map the fields to your sheet columns. The structural issue is that Zapier runs one record at a time.

Running a query that returns 500 rows means 500 task executions. Your Zap history becomes a wall of green checkmarks that masks the one row that returned a null and got silently skipped.

You probably just need the query results in the sheet. You probably have no idea what a dataset query payload looks like — and there's no reason you should. So you hand it off to whoever on your team handles automations, and now you're waiting for them to build it, test it, and tell you it's ready. Which might be this week or might be next month.

And once you need to filter across result sets, pivot by a dimension, or join two saved questions — you've hit the ceiling of what Zapier was designed for.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable Metabase-to-sheet workflows was a category of add-ons that let you store an API configuration — your Metabase URL, your card ID, your column mappings — and run it on demand. You configured the fields once, saved the template, and ran it when you needed fresh data.

That was a real improvement over manual exports. The schema stayed consistent, the team didn't have to remember which CSV format Metabase used this month, and running the pull was a single button click.

But the configuration was on you. You mapped the columns. You handled the authentication. You decided which card to run against which sheet range. The tool moved the data; the operator still did the thinking. And if someone renamed a column in the Metabase question, the config broke until you went back in and realigned it.

This is the previous generation of the solution. It reduced the manual labor but didn't eliminate the mental overhead.

The Easy Way: Using SheetXAI in Google Sheets

There is a different way entirely. SheetXAI is an AI agent that lives inside your Google Sheet. It reads what's already in the sheet, understands the context, and through its built-in Metabase integration can run queries, pull saved question results, and write data back — without any configuration template on your part. You just ask.

Example 1: Pull a SQL query result into the sheet

Run the SQL query SELECT user_id, plan, mrr, signup_date FROM subscriptions WHERE status = 'active' against Metabase database ID 3 and write the results into Sheet1 starting at row 1 with column headers

The results land in Sheet1 with headers matching the query's column aliases. No CSV, no import dialog.

Example 2: Export a dashboard's cards to separate tabs

Fetch Metabase dashboard ID 14, run each card's query, and write the results into separate tabs named after each card — include headers on each tab

Each card becomes its own tab. The data is live from the database, not a cached screenshot.

Try It

Get the 7-day free trial of SheetXAI and open any Google Sheet you use for reporting, then ask it to pull a Metabase query result or saved question directly into the sheet. The Metabase integration is included in every SheetXAI plan.