Your Metabase server is running and the vibe-code agent is sitting in the Open WebUI chat, able to read the app config, query your database, and restart services. You do not need to memorize the query builder to get your money’s worth — you need good prompts. Here are ten everyday jobs you can hand over today.

1. Turn a Plain-English Question into a Saved Question

Ask for a number and get a chart that stays fresh. The agent inspects your schema, writes the SQL (or builds the GUI question), runs it, and saves it into a collection so you can revisit it later. Example: “Show me revenue per month for this year and save it as a question called Monthly revenue in the Sales collection.” If the number looks off, ask it to show the SQL and walk you through the joins and filters. Most simple questions come back correct on the first try; tricky ones need one round of correction.

2. Build a Dashboard with Working Filters

Solo questions are fine, but dashboards are where Metabase earns its keep. Have the agent assemble your saved questions onto one dashboard, then add a date filter and a category filter wired to every card. Example: “Build a Sales overview dashboard with the revenue, orders, and top-products questions, and add a date-range filter that applies to all of them.” Ask it to test each filter before calling it done — a filter that only controls half the cards is the classic dashboard bug. Once it works, the same filter wiring carries over to subscriptions.

3. Get the Morning Numbers by Email

A dashboard subscription emails a snapshot of a dashboard on a schedule — daily at 8am, a Monday summary, whatever you need. The agent sets it up and attaches your team. Example: “Email the Sales overview dashboard to me every weekday at 8am.” It will confirm SMTP is configured first, because without that the subscription silently goes nowhere. If email is not set up yet, that is fix number one and the agent can handle it too.

4. Set an Alert When a Number Crosses the Line

Metabase alerts watch a time-series question and email you when it goes above or below a threshold — or, for raw-SQL questions, when any row comes back at all. That second mode is handy for error spikes or “no orders in 6 hours.” Example: “Alert me when daily revenue drops below $500 and email the ops group.” Have the agent show you the alert’s schedule and confirm the threshold sits on the right column before you rely on it. Alerts are cheap to create and easy to edit, so start generous and tune later.

5. Chase Down a Number That Looks Wrong

When a chart says something impossible, the fastest fix is to ask. The agent can read the question’s SQL, re-run pieces of it, compare against the raw tables, and tell you whether the bug is in the query or in your data. Example: “This dashboard says we had 40 refunds yesterday — check whether that is real or the filter is wrong.” It usually finds the problem in minutes because it can inspect both Metabase and the database underneath. This one request teaches you more about your data than any documentation could.

6. Tidy the Question Pile

Six months in, every Metabase instance has a graveyard of duplicated and abandoned questions. Have the agent audit your collections: find questions nobody viewed in 90 days, flag near-duplicates, and archive the junk. Example: “Find all questions in Our analytics that haven’t been viewed in 3 months and list them before archiving anything.” Review the list yourself before it deletes — some old questions exist for quarterly reports. A quarterly run keeps the place searchable.

7. Connect a Database or Fix a Stale One

Adding a data source is a form and a connection string, but it is easy to get wrong. The agent can register the database through the admin panel, test the connection, and trigger an initial sync so your tables appear. Example: “Connect our staging Postgres at this host as a new database called Staging and sync it.” If an existing connection starts failing, the agent can read the error, check whether the password expired, and re-sync the schema. It can also schedule periodic re-syncs if your warehouse changes often.

8. Fix Confusing Table and Column Names

Your warehouse has tables like o_12_cust and columns nobody understands. The agent can rename them inside Metabase without touching the database itself, set human-readable display values, and add descriptions so the team knows what qty_net_v2 actually means. Example: “Rename the columns in the orders table to plain English and add a one-line description to each.” This pays off every time someone builds a new question, because the query builder shows your names instead of the schema’s. Do it once, early, before bad names spread into fifty dashboards.

9. Onboard a Teammate with the Right Access

New hire needs Metabase? The agent can create the account, add them to the right groups, and make sure they land in a collection with the questions they need — nothing more. Example: “Add maria@ourcompany.com to the Sales team group and make sure she can view the Sales collection.” It can also sanity-check that the default All Users group does not accidentally have edit access to everything. Two minutes of prompting replaces a permissions meeting.

10. Share One Dashboard with an Outsider, Safely

Sometimes a supplier or investor needs exactly one dashboard and nothing else. Metabase public links give view-only access to a single dashboard with no login required. Example: “Create a public link for the Investor metrics dashboard and show me how to turn it off later.” Have the agent verify that public sharing is disabled everywhere else, because public means public — anyone with the link can see it. When the review is over, ask it to revoke the link and confirm it is dead.

Start with one or two of these and watch the agent show its work. Everything above is reversible, and you will learn the tool by delegating to it. Metabase on OpenSysLab