Start free
Read & reportControlled changes

See your Metabase numbers in AWS S3.

Review Metabase cards, dashboards and connected databases, with controlled title and description updates from Datapipe.

  • Invoices and payments in a sheet that refreshes itself
  • Monthly finance reports without exporting
  • Ask an AI assistant which invoices are overdue
MetabaseAWS S3AWS S3

Start free Connect Metabase

Updated November 2026

Metabase reportSample data
Question nameVisualization typeArchived
1,2401,240false
640640640
210210210
Refreshes on your schedule in AWS S3

Who uses Datapipe with Metabase

Finance leads

Track invoices and payments without manual exports.

Agency owners

See billed work and collected cash for each client.

Founders

Get a monthly money summary in plain words.

What you can do with Metabase

Read and report

Read cards, dashboards and databases using your Metabase instance URL and X-API-Key.

  • Saved questions (cards)
  • Dashboards
  • Connected databases

Explore metrics and dimensions

Controlled changes

  • Update saved question
  • Update dashboard details

Changes stay off until you allow them. Allowed changes apply to Metabase right away, and history keeps the values before and after.

See what you can change

Full read details

Optional card and dashboard metadata updates stay off until enabled.

Examples for your team

Read & report

Audit Metabase questions and dashboards

Combine saved question view counts, visualization types, dashboard card counts and connected database engines.

  1. Scheduled refresh
  2. Latest Metabase data
  3. Updated report
Controlled change

Update a Metabase saved question title or description

A teammate updates a question's name or description, and Metabase applies the change via PUT.

  1. Allowed
  2. Applied
  3. Recorded

Limit: History records the before and after values.

Fix things in Metabase without opening it

Spot it, fix it

See the problem in your report, then make the fix in Datapipe instead of opening Metabase, finding the record and retyping it.

More people can help

Teammates and AI tools you allow can make changes without getting edit access to Metabase.

You decide what can change

Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.

Jobs you can stop doing by hand in Metabase

Update saved question

  • Rename a Metabase saved question

    TodayOpen the question in Metabase, click its title, type the new name, and save.

    With DatapipeReview BI cards in your Metabase report and standardize the question title from Datapipe with an approval trail.

Exactly what this can change

Changes the title or description of one saved question in Metabase. Its query and results stay the same.

Supported fields: Question name, Description.

Update dashboard details

  • Update a Metabase dashboard description

    TodayOpen the dashboard in Metabase, click the info icon, edit the description, and save.

    With DatapipeKeep dashboard descriptions aligned with current KPI definitions from Datapipe.

Exactly what this can change

Changes the title or description of one Metabase dashboard. Its cards and layout stay the same.

Supported fields: Dashboard name, Description.

Recorded changeExample

MetabaseUpdate saved questionQuestion #42 · Monthly Net Revenue · made by Elena Vance

FieldBeforeAfter
nameNet Rev (Old)Monthly Net Revenue

Applied to MetabaseRecorded in Changes history

You control who can change what

  1. A change is allowed for this data source
  2. A teammate or AI tool makes it
  3. It applies right away, or waits for approval if you set that
  4. Recorded with the values before and after

Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?

Provider rules and limits

Provider permissions still apply, and automations in Metabase may react to changes.

Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.

Before you connect

What you need

An API key or token from your Metabase account.

Read and write

Read access for reports. The 2 change actions need edit access in Metabase and stay off until the owner, an admin or a project manager allows them.

Limits and exclusions

Question results and the data behind them are not read.

Full details and limits

Saved questions (cards), dashboards, and connected database engines from your Metabase instance.

Reporting reads cards, dashboards, and databases using your Metabase API key. Optional question and dashboard title or description updates are off until allowed for this data source, and every change is recorded in history. Underlying SQL queries and permissions are not altered.

One Metabase instance per data source. Question results and the data behind them are not read.

Reports you can build

3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.

What each dataset reports
  • Saved questions (cards)

    Metabase saved questions with display visualization type, collection ID, archive state, and query count.

  • Dashboards

    Metabase dashboards with collection placement, archive status, and card counts.

  • Connected databases

    Database engines configured in Metabase along with sync status and table counts.

Metrics and dimensions

18 report fields across 3 datasets.

Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.

Send Metabase data anywhere

Ask AI about your data

Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.

AI tools can also make allowed Metabase changes. They can never widen their own access.

Summarize active Metabase cards, dashboards, and connected database engines.

Monthly Net Revenue leads with 482 views; 18 active dashboards are backed by Postgres and BigQuery.

Better than exporting by hand

Start from a goal

How it works

  1. Create a project and choose Metabase in Data sources.

  2. Pick where it goes. This one sends the numbers to AWS S3.

  3. Pick where it goes. Choose questions, dashboards or databases and a destination.

Sample report

Metabase reportSample data
Question nameVisualization typeArchivedView countDashboard nameCards countUpdated date
1,2401,240false12,4801,2401,240Oct 27
6406406408,240640640Oct 28
2102102103,110210210Oct 29

Sample numbers, so you can see the shape. Your report uses your accounts.

Works well with Metabase

Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.

Questions

Free to start. Paid plans add more data sources and refresh faster.

Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.

No. Name a project, add a data source, then choose a report and destination.

OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.

The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.

No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Metabase account. Nobody else gets a Metabase login from this.

Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.

Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.

Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Metabase received it, the request is marked Uncertain and is never retried automatically, so you can check Metabase first.

Yes. Datapipe reads the reports on this page and can make 2 kinds of change: update saved question; update dashboard details. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.

This page lists 18 report fields across 3 datasets. You pick the columns when you build the report.

Saved questions (cards), dashboards, and connected database engines from your Metabase instance. Account permissions and the records available from the provider determine which rows can be read.

One for each Metabase account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.

Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.

Try Metabase with sample data first

Build the report first, then add Metabase when you are ready.

Start free Add data source