Connect Metabase to Copilot
Send Metabase users, cards, collections and 4 more data types to Copilot on a schedule. Refresh as often as every 15 minutes.
What changed in our Metabase data this week?
How to connect Metabase and Copilot
4 steps. You can preview the Metabase data in Coupler.io before anything reaches Copilot.
Step 1 of 4
Connect Metabase
Enter your Metabase metabase instance API URL and API key. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the Metabase data you want in Copilot.
Step 3 of 4
Connect Copilot
In Copilot Studio, add a Model Context Protocol tool to your agent with the Coupler.io MCP server URL from the destination step. Each user signs in to Coupler.io once.
Step 4 of 4
Set a schedule
Copilot sees the data as of the last run. Run it as often as every 15 minutes.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your Metabase integrations with these destinations
Get the most of Metabase to Copilot integration
Gather data
Understand data
Automate data
Act on data
7 data types, including Users, Cards, Collections, Dashboards and Databases.
With your Metabase metabase instance API URL and API key, entered once when you add the connection.
No. The data stays in Coupler.io, and Copilot queries it read-only when you ask a question. It can't edit or delete Metabase rows.
Microsoft Copilot Studio. Add Coupler.io to your agent as an MCP tool, and the agent can query your Metabase data.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example 100ms or Amazon Seller Central, and join or append them before the data reaches Copilot.