Automated Looker Studio Data Source Audit
Every Monday, WebRun opens Looker Studio, walks the reports you rely on, refreshes each one, records any data source throwing an error or returning nothing, notes the owner and sharing settings in Notion, and messages you on Telegram the reports to fix before anyone opens them.
How do I find Looker Studio reports with broken data sources?
Every Monday WebRun opens Looker Studio, refreshes the reports you rely on, and records any data source that errors, hits a permission problem, or has gone stale. It logs each finding with its owner in Notion and messages you the fix list on Telegram, so nobody presents a chart built on dead data.
- Broken reports are found before a stakeholder opens one
- Every failing source has a named owner in the message
- Stale data is flagged separately from hard errors
Built for data analysts · BI teams · marketing analysts · operations reporting
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
lookerstudio.google.comin a real browser with your saved login - no setup, no API keys. -
1
Looker Studio - check reports and data sources
lookerstudio.google.com
WebRun opens Looker Studio to check reports and data sources. - Open Looker Studio and list the reports you have marked as important
- Open each report and trigger a data refresh
- Record any data source that returns an error, a permission problem, or no rows
- Note the last successful refresh date on each source
- Capture the report owner and who the report is shared with
- Change nothing in the report. WebRun only opens, refreshes, and reads
Done when Every watched report has a refresh result and its data sources have been checked.
-
2
Notion - log broken sources and owners
notion.so
WebRun opens Notion to log broken sources and owners. - Keep one row per report with its data sources, refresh result, and owner
- Mark rows red when a source errors and amber when it has not refreshed in a fortnight
- Record how long a report has been failing so a chronic one stands out
- Clear rows that refreshed cleanly this week
Done when The Notion table shows the current health of every watched report.
-
3
Telegram - send the fix list
telegram.org
WebRun opens Telegram to send the fix list. - Message the list of reports that failed to refresh, with the failing source named
- Add the reports whose data has gone stale but has not errored yet
- Put the owner next to each so it is clear who fixes it
- Say so plainly when every report refreshed cleanly
Done when You know which reports are broken and who owns each one.
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 reconnect my reports?
No. WebRun opens each report, refreshes it, and reads the result. Reconnecting a data source, changing credentials, or editing a chart stays with the report owner, and nothing is shared or sent to viewers.
How does it tell stale from broken?
Broken means the data source returned an error, a permission problem, or no rows on refresh. Stale means it still works but has not refreshed in a fortnight. Both appear in the message, marked differently.
Does it send anything to the people the report is shared with?
No. The only message goes to your own Telegram, and the Notion table is internal. Report viewers see nothing from this workflow.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.