Catch failed Looker deliveries before stakeholders do
Every morning, WebRun opens Looker, reviews the scheduled deliveries that ran overnight, records every failure or skipped send in Airtable with its dashboard and owner, and posts a short fix list into your Notion analytics page.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out when a Looker scheduled delivery fails?
WebRun checks your Looker scheduled deliveries every morning and reads the result of each overnight run. It logs every failed or skipped delivery in Airtable with its dashboard, owner, and error text, flags repeat offenders, then posts a short fix list into Notion so broken reports get owned before stakeholders notice.
- Broken report deliveries are caught the same morning, not by a stakeholder
- Every failure has a named owner in Airtable
- Repeat failures surface at the top instead of hiding in the noise
Built for data teams · analytics engineers · BI administrators · data platform owners
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
looker.comin a real browser with your saved login - no setup, no API keys. -
1
Looker - review overnight deliveries
looker.com
WebRun opens Looker to review overnight deliveries. - Open Looker and go to the admin view of scheduled deliveries
- List the schedules that ran since the last check and read each result status
- Capture the dashboard or Look name, the recipient, the owner, and the error text for anything that failed or was skipped
Done when Every overnight delivery has a status, and each failure has its dashboard, owner, and error captured.
-
2
Airtable - log every failure
airtable.com How to Automate Airtable
WebRun opens Airtable to log every failure. - Open the delivery health base in Airtable
- Add one row per failed or skipped delivery with the date, dashboard, owner, recipient, and error text
- Match against yesterday's rows and mark anything failing two runs in a row as repeating
- Close out rows whose schedule succeeded today
Done when Airtable holds one row per failure with a repeat flag, and fixed schedules are closed.
-
3
Notion - post the fix list
notion.so How to Automate Notion
WebRun opens Notion to post the fix list. - Open the analytics team page in Notion and add today's entry
- List the failed deliveries with their owner, putting repeating failures at the top
- Note how many schedules ran clean so the page shows the trend, not just the problems
Done when Today's fix list is on the Notion page with repeating failures first.
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 change or rerun my Looker schedules?
No. WebRun only reads delivery results in Looker. It never edits, pauses, reruns, or deletes a schedule, and it never sends a report to a recipient. Any rerun stays a human decision recorded on the Notion list.
How does it know a failure is getting worse?
It compares today's failures against the rows already in Airtable. Anything that failed on two consecutive runs is flagged as repeating and sorted to the top of the Notion fix list.
What happens once a schedule is fixed?
The next run reads the live status in Looker, sees the delivery succeeded, and closes the Airtable row, so the fix list only ever shows what is still broken.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.