How to Connect Metabase to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of Metabase

You have an Excel workbook full of data — revenue cohorts, churn breakdowns, pipeline metrics — and you need it either loaded into Metabase or extracted from a query result. The default path involves a Metabase CSV export, a local file save, an Excel import, a column header cleanup, and a paste into the right range. Then the underlying query changes and you repeat it.

Metabase is good at letting business users run SQL and saved questions against production data without DBA access. But the distance between "Metabase ran the query" and "the workbook has the answer" is still manual by default. Below are four ways teams typically bridge it.

Method 1: Manual CSV Export

The standard move for Excel users. You run the query in Metabase, download the CSV, open it in Excel, copy the rows, and paste them into your workbook. For a one-time pull, this is fine.

The friction accumulates when it becomes a recurring task. The CSV filename changes every export. The column order in the Metabase result shifts when someone edits the saved question. Your paste overwrites a formula you forgot was in row 1. You fix it, document the workaround, and watch it break again three weeks later when the query gets a new filter applied.

The work isn't hard. It's just relentless, and it crowds out the analysis you were actually hired to do.

Method 2: Power Automate

Power Automate has connectors that can reach Metabase via HTTP actions. You can schedule a flow, call the Metabase API, parse the JSON response, and write the results into an Excel workbook stored in OneDrive or SharePoint.

Before you go further: do you know how to construct a Metabase API session token? Do you know how to parse a nested JSON array into Excel rows using Power Automate's Apply to Each action? Do you know what to do when the response schema changes and your flow silently writes null into every cell? If those questions feel foreign, skip ahead to Method 3 or 4. This approach is built for people who configure automations regularly.

If you're still here: the flow can work. You authenticate, call the dataset endpoint, loop over the rows array, and write each value into the right column. The friction is in the maintenance.

Power Automate flows that talk to APIs tend to break quietly. A column rename in the Metabase question produces a schema mismatch that your flow doesn't surface — it just writes nothing, or the wrong thing, and you find out when someone asks why the report looks wrong.

You probably just need the query results in the workbook. You probably have no idea how to build an HTTP action flow in Power Automate — and that's not a gap you should have to close just to get data into Excel. So the task goes to IT or to whoever maintains the company's Power Automate environment, and you wait.

And once you need to join two query results, apply conditional logic, or handle a Metabase question that returns different columns depending on the filter — you've hit a wall.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable Metabase-to-workbook workflows was a category of add-ons that let you save an API configuration — base URL, card ID, column mapping — and re-run it on demand. You set it up once and refreshed the data with a click.

That was a meaningful step up from manual exports. The schema stayed predictable, the team could refresh without rebuilding, and you didn't have to touch the CSV pipeline every time.

But someone had to build the configuration. Someone mapped the columns, handled the auth, and decided which Metabase question fed which workbook range. The tool passed the data through; the operator still did the architectural thinking. And the moment the Metabase question's output changed shape, the config broke.

This is the previous generation. It worked, but it required a keeper.

The Easy Way: Using SheetXAI in Excel

There is a fundamentally different approach. SheetXAI is an AI agent that lives inside your Excel workbook. It reads the workbook, understands what you're looking at, and through its built-in Metabase integration can run queries, pull saved question results, and write the data into your workbook — no configuration template, no connector setup. You just ask.

Example 1: Pull a SQL query result into the workbook

Run the SQL query SELECT cohort_month, COUNT(user_id) as users, SUM(mrr) as total_mrr FROM subscriptions GROUP BY cohort_month ORDER BY cohort_month against Metabase database ID 2 and load results into Sheet1 with headers

The results land in Sheet1 with the column headers from the query. No CSV, no import wizard, no paste.

Example 2: Export a dashboard's cards to worksheets

Fetch Metabase dashboard ID 8, run each card's query, and write the results into separate worksheets named after each card

Each card gets its own worksheet. The data reflects the current state of the database, not a screenshot from last week.

Try It

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