# Metabase integrations: questions and dashboards

> Create a question, create a dashboard and add a database connection in Metabase, and start a workflow when Metabase sends “Alert triggered”.

**Canonical page:** https://tray.ai/connectors/metabase-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Metabase is a business intelligence tool, available open source or as a hosted service, that connects to your databases so teams can ask questions, build charts, and share dashboards. Tray.ai connects to Metabase through the HTTP Connector, so your workflows can call the Metabase API alongside the rest of your stack.

## Use cases

### Questions

Read and create questions in Metabase from any Tray.ai workflow. The Metabase API covers calls such as list questions and create a question.

- List questions
- Create a question

### Dashboards

Create dashboards in Metabase from any Tray.ai workflow. The Metabase API covers calls such as create a dashboard and add a question to a dashboard.

- Create a dashboard
- Add a question to a dashboard

### Databases

Create databases in Metabase from any Tray.ai workflow. The Metabase API covers calls such as add a database connection and validate connection details.

- Add a database connection
- Validate connection details

### Users

Create and update users in Metabase from any Tray.ai workflow. The Metabase API covers calls such as create a user and update a user.

- Create a user
- Update a user
- Disable a user

## Challenges Tray.ai solves

### Keeping Metabase credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Metabase credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Metabase API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Metabase API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Metabase?

Yes. Tray.ai connects to Metabase through the HTTP Connector, which calls the Metabase API directly. Any call the Metabase API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Metabase?

The Metabase API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Metabase connector?

Metabase runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Metabase connector from the Metabase API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/