Runner.Featured workflow
Business Intelligence for Board Prep
Board decks get built from live data instead of manual screenshots and copy-paste.
CONNECTOR
MetabaseMetabase connector
Run saved queries, browse dashboards, and pull business intelligence into the workflow.
Runner uses Metabase through the Composio toolkit for dashboard queries, saved question execution, and SQL-based data exploration with row limits.
Metabase in real workflows
The app page is only useful if it shows how Metabase fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
+New Session
Sessions
Connected appsMetabase
Google Sheets
Slack
MetabaseGoogle SheetsSlack+
Connect a new appWhat would you like to do?
Connected apps
Apps used with Metabase
Why it's better
Metabase is more useful inside a workflow
- Search and run existing saved questions and dashboards.
- Browse database schema to identify tables and columns.
- Write custom SQL queries with proper row limits.
Common pairings
Metabase often works with
Related workflows
Public workflow pages where Metabase is part of the connected stack.
What Runner can do with Metabase
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
Metabase
Run a saved question
"Run the 'Monthly Active Users' question from the product dashboard."
Business metrics become part of the operating context without opening Metabase.
Metabase
Write a custom query
"Query the events table for conversion rates by channel over the last 30 days, limit 200 rows."
Custom data analysis happens inside the workflow instead of switching tools.
Metabase
Browse the database schema
"Show me the tables and columns available in the analytics database."
Schema discovery happens inside the workflow before writing any queries.
How this connector is wired in Runner
Provider
Metabase
Category: Analytics.
Backend
Composio toolkit
Backed by the `metabase` toolkit in Runner's backend catalog with question, dashboard, and database operations.
What to expect when Runner uses Metabase
Operational note
Metabase
Always search for existing saved questions first — avoid creating duplicates.
Operational note
Metabase
Always include row limits on custom queries. Unbounded queries can crash the instance.
Testimonials
People using Runner to get more done with Metabase
The value is the same across connectors: real context in, real work out, no copy-paste operating model.
“I got hours back every week. Runner handles the follow-through work that used to sit open across tabs and docs.”
Jordan Rogers
@jordanrogers
“It gives me one place to work across email, calendar, and docs. The time savings are real.”
Lynn Marshall
@lynnmarshall
“I stopped losing deals to slow follow-up. Runner drafts the reply and schedules the next step before I forget.”
Danielle Okafor
@danielleokafor
“Runner connects my CRM, email, and meeting notes so I actually prep for calls instead of winging it.”
Aisha Patel
@aishapatel
“What used to take half a day now takes one focused pass in the morning.”
Rajat Singh
@rajatsingh
“Meeting follow-up used to die in my notebook. Now the recap, emails, and calendar items happen before I leave the room.”
Ethan Park
@ethanpark
“I tried every productivity tool on the market. Runner is the first one that actually finishes work instead of just organizing it.”
James Wright
@jameswright
“Board prep went from a full Sunday to a one-hour Monday morning workflow. The context is already assembled.”
Priya Nair
@priyanair
“The morning briefing workflow changed how I start every day. I see blockers, priority threads, and follow-ups before the first meeting.”
Sarah Kim
@sarahkim
“The double opt-in intro workflow is the single most useful thing I have run this quarter. Warm intros used to take 20 minutes each.”
Marcus Chen
@marcuschen
“Investor updates that used to take a full day now come together in 45 minutes from real data.”
Oliver Reeves
@oliverreeves
Use Metabase inside a real workflow
Download Runner to connect Metabase to the rest of your workflow instead of treating it like another isolated tab.