Automated Looker Studio Report Exports
Every Monday, WebRun opens each of your Looker Studio reports, checks that every data source loaded without an error, sets the date range to last week, exports the report to PDF, files it in a dated Google Drive folder, and posts Slack the link with the headline numbers and any chart that failed to load.
How do I automatically export and share Looker Studio reports weekly?
Every Monday WebRun opens your Looker Studio reports, checks each data source loaded cleanly, exports the report to PDF, and files it in a dated Google Drive folder. It then posts Slack a link with the headline numbers and flags any chart showing a data source error.
- The weekly report lands before anyone asks for it
- Every week's PDF is archived and findable in Drive
- Broken data sources are caught before a decision is made on bad numbers
Built for analytics teams · marketing agencies · operations managers · client reporting teams
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 - refresh and export the reports
lookerstudio.google.com
WebRun opens Looker Studio to refresh and export the reports. - Open each report on your reporting list in Looker Studio
- Set the date range control to last week and let every chart finish loading
- Note any chart showing a data source or configuration error rather than data
- Capture the headline scorecard figures from the top of the report
- Export the report to PDF using the Share menu
Done when Every report on the list has a fresh PDF and its headline numbers noted.
-
2
Google Drive - file the weekly PDFs
drive.google.com
WebRun opens Google Drive to file the weekly PDFs. - Open your Reporting folder in Google Drive and create a subfolder for the week
- Save each PDF with the report name and the week ending date in the filename
- Keep the previous weeks in place so the folder builds a running archive
- Append a row to the reporting index sheet with the report name, week and file link
Done when This week's PDFs are filed and indexed in Drive.
-
3
Slack - post the link and headlines
slack.com
WebRun opens Slack to post the link and headlines. - Post one message per report to your analytics channel with the headline figures
- Show the change against the previous week beside each number
- Link the PDF in Drive and the live Looker Studio report
- Call out loudly any chart that failed to load, because a broken source means the numbers are not trustworthy
Done when The analytics channel has this week's reports with links and headline numbers.
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
Does it edit my Looker Studio reports?
No. WebRun views each report, sets the date range control and exports a PDF. Charts, data sources, filters and layout are never changed.
Will it share reports outside my team?
No. PDFs are saved into a Drive folder you already control and the Slack post goes to your internal channel. WebRun does not change sharing permissions or email anyone externally.
What happens when a data source breaks?
The broken chart is called out at the top of the Slack post and noted on the archived PDF, so nobody reads a number that quietly failed to load.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.