Nexra
Start in the sandbox
All connectors

Metabase

Analytics, databases & data platforms

Bring your business data together in Metabase, and act on it in the apps your team already uses.

13 ways to read, 2 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Metabase with Nexra

Connected, approved, proven.

The things teams do most with Metabase, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create a collectioncollections.createApproval by rule
  • Save a new questionquestions.createApproval by rule
  • List question alertsalerts.listRead

Example flow

  1. Metabase · List question alertsalerts.listDone
  2. Metabase · Create a collectioncollections.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Metabase.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Metabase
  • Metabase's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Metabase: run saved questions and dashboard cards, read collections, questions, dashboards, alerts and subscriptions, and save new collections and questions.

Metabase API docs
Source actions
13
Destination actions
2
Data types
11

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

alerts1
  • List question alertsSource

    Lists alerts on saved questions (who gets them is summarised as a count). Admin keys see every alert.

collection items1
  • List what is in a collectionSource

    Lists the questions, dashboards, models and sub-collections in one collection (use root for the top level).

collections2
  • Create a collectionDestinationProvider duplicate protectionApproval before production

    Creates a collection (folder) at the top level or inside another collection.

  • List collectionsSource

    Lists the collections (folders) the API key can see.

current user1
  • Check the connectionSource

    Shows the Metabase account the API key acts as and whether it is an admin.

dashboard card results1
  • Run a dashboard cardSource

    Runs the question on one dashboard card with the dashboard's filter values and returns its rows.

dashboard cards1
  • List a dashboard's cardsSource

    Lists the cards on a dashboard, each with the saved question it shows, so a flow can run them.

dashboard subscriptions1
  • List dashboard subscriptionsSource

    Lists scheduled dashboard emails and Slack messages (recipients summarised as a count).

dashboards2
  • Get a dashboardSource

    Gets one dashboard with its filters, tabs and cards.

  • List dashboardsSourceIncremental

    Lists dashboards, optionally only those edited since a time.

databases1
  • List databasesSource

    Lists the databases connected to Metabase that the API key can see.

question results1
  • Run a saved questionSource

    Runs a saved question and returns its rows (up to 2,000), optionally with filter values.

questions3
  • Save a new questionDestinationProvider duplicate protectionApproval before production

    Saves a new question built with Metabase's notebook editor query format (MBQL) into a collection. SQL questions are not accepted.

  • Get a saved questionSource

    Gets one saved question with its filters (parameters).

  • List saved questionsSourceIncremental

    Lists saved questions, newest edits included, optionally only those edited since a time.

Access and limits

Authentication
Metabase API key
Plans and access
API keys are available on every Metabase plan, Metabase Cloud and self-hosted (open source included). An admin creates the key and assigns it to one group; the key sees and does only what that group may. Native SQL is not offered.
Test environment
Use a Metabase Cloud trial or a local open-source Metabase with the Sample Database, and a key in a test group, before connecting production.
Rate limits
Metabase documents no API rate limit; self-hosted capacity depends on your server and Metabase Cloud on your plan. Nexra backs off on 429 and 5xx answers.
Pagination
Search and collection items use limit and offset with a reported total; query results are one page of up to 2,000 rows.
Provider events
Metabase has no change webhooks. Alerts and subscriptions send emails, Slack messages or HTTP posts of results on a schedule. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Query results are capped at 2,000 rows per run (Metabase's own API limit for raw rows by default); larger results are marked truncated. File exports are not offered.
  • Native SQL is not offered: questions are created only from structured (MBQL) queries, and SQL questions can still be run as saved questions.
  • Changed-since reads use Metabase search's last-edited filter, which takes a time without a time zone; Nexra re-reads a wider window and removes duplicates.
  • Alerts need Metabase 0.54 or later; dashboard subscriptions use /api/pulse, which Metabase plans to replace.
  • Metabase served under a URL path (for example https://example.com/metabase) is not supported.
  • Recipients of alerts and subscriptions are summarised as counts; their names and emails are not returned.
  • Intentionally excluded: creating, changing or sending alerts and subscriptions (they message people), deleting, archiving or moving anything, public and embed links, users, groups, permissions and API keys, database connections, syncs and scans, native SQL, and ad-hoc queries.

Developer reference

  1. Create the Metabase credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Metabase, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Metabase docsAPI referenceMetabase docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/metabase and the Connections API.