Find the broken charts on your dashboards before your team does
Every Monday, WebRun opens Metabase, loads each dashboard your team relies on, records which cards error out, time out, or come back empty, creates one Trello card per broken question with the dashboard and owner attached, and sends the data team a short WhatsApp summary of what needs fixing.
- 7-day free trial
- Under $0.01 per run
- Cancel anytime
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
metabase.comin a real browser with your saved login - no setup, no API keys. -
1
Metabase - load every dashboard and check each card
WebRun opens Metabase to load every dashboard and check each card. - Open Metabase and go to the collections holding your team dashboards
- Load each dashboard on the watch list and let every card finish running
- Record any card that returns an error, times out, or comes back with no rows
- Note the dashboard name, the question name, and the collection it lives in
Done when Every watched dashboard has been loaded and its failing cards recorded.
-
2
Trello - open a card per broken question
WebRun opens Trello to open a card per broken question. - Open your data team board in Trello
- Create one card per broken question, titled with the question and its dashboard
- Put the error text and a direct link to the question in the card description
- Skip questions that already have an open card so nothing is duplicated
Done when Every newly broken question has exactly one open Trello card.
-
3
WhatsApp - send the data team the fix list
WebRun opens WhatsApp to send the data team the fix list. - Send the data team group a short summary: how many cards were checked and how many are broken
- List the top offenders by dashboard so the busiest one gets fixed first
- Note anything that has been broken for more than one week
Done when The data team has this week's dashboard health summary on WhatsApp.
How do I find broken Metabase dashboard cards before my team reports them?
WebRun opens Metabase every Monday, loads each dashboard on your watch list, and records every card that errors, times out, or returns nothing. It opens a Trello card per broken question with the error and a direct link, then sends the data team a WhatsApp summary of what needs fixing this week.
- Broken charts are caught on Monday morning, not by an executive mid-meeting
- Every failing question arrives as a Trello card with the error already attached
- Long-broken dashboards are called out instead of quietly ignored
Built for data teams · analytics engineers · BI leads · operations analysts
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it edit or delete any of my questions?
No. WebRun only loads dashboards and reads what each card returns. It never edits a question, changes a dashboard, or deletes anything in Metabase. Fixes are logged as Trello cards for a human to action.
How does it tell a broken card from an empty one?
It separates the two. Query errors and timeouts are reported as broken, while cards that run fine but return no rows are listed separately, because an empty result is sometimes correct.
Can I limit it to the dashboards that matter?
Yes. Give WebRun a watch list of collections or specific dashboards and it checks only those, which keeps the run short on large instances.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.