Docs / Data sources / Metabase

Metabase

Business software

Built when you ask for it

Sync Metabase card, dashboard, collection, and user data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Metabase connector syncs your BI platform metadata into analytics-ready tables in your data warehouse. Pull cards, dashboards, collections, and users from the Metabase API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Cards
  • Dashboards
  • Collections
  • Users

How it gets built

  1. Choose Metabase when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Metabase's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Metabase itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (X-Api-Key header), session token, or JWT on Pro/Enterprise. Not a hosted vendor API: an admin generates the key inside their own Metabase instance under Admin > Settings > Authentication > API Keys.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Metabase connector?
Not as a finished connector yet. Ingest builds it from Metabase's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Metabase data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Metabase API documentation: https://www.metabase.com/docs/latest/api

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Metabase