Email a weekly Google Sheets report: choose the right workflow.

"Email me my spreadsheet every week" hides several possible requirements. One person wants to know when a status becomes overdue. Another wants a dashboard PDF. A third wants five business metrics in the email body so nobody has to open a file. Those outputs need different workflows; choosing a script before choosing the output is how a small automation becomes a maintenance project.

Start with a sentence that names the source, the reporting period, the recipient and the output. For example: every Monday, email the operations address the prior completed week's sales total, average response time and three largest clients, using the numbers already checked in our Sheet. That is a much more useful specification than "automate reporting".

Google Sheets has conditional notifications on eligible work or school accounts. A rule can watch a range or column and notify selected addresses when a value changes and meets a condition. If the job is "tell the owner when this status becomes Completed", inspect that option before installing code. Availability and recipient restrictions matter; check the current documentation and your account.

That is not the same contract as a scheduled summary of sums, averages and comparisons. An event-driven notification answers "what changed?" A weekly digest answers "what do these numbers mean for this reporting period?" Pick the former when you need the event, not because its email happens to look like a report.

Google's Data Studio report delivery can email a scheduled PDF and a link to the original report. If your team already uses a dashboard and wants its familiar charts, that can be a better fit than reconstructing it in an HTML email. Check report permissions, recipient rules and the delivery options available to your account rather than assuming every schedule feature is included.

The tradeoff is the artifact: a dashboard report rather than an editable email template. Do not buy an Apps Script pack just to reproduce a scheduled export that your existing reporting tool already handles. Conversely, building a dashboard solely to send four numbers might be more work than maintaining a small script.

A custom script makes sense when the values already exist in Sheets and you need control over aggregation and email layout. You can write it yourself, start from a reviewed generated draft, or buy a workflow pack. In every case, you still own the source data and setup. None of those choices magically collects missing sales or analytics data.

Our Auto-email Weekly Digest is one such self-install pack, not a reporting service. It reads configured ranges and supports sums, averages, a last-two-values comparison and top-N values. A range such as B2:B8 stays B2:B8 next week: it does not advance itself. Use a maintained summary tab or deliberately update the configuration. Otherwise a perfectly functioning trigger will faithfully email the wrong week.

The public demo uses fictional rows and the actual email renderer. Offline checks and sandbox download tests have passed. As of publication, we have not verified Google execution, received mail or an independent customer installation. The demo is evidence of format and setup, not evidence of a successful real-world deployment.

Apps Script's clock-trigger builder requires a recurrence when using atHour or nearMinute. A weekly Monday trigger needs everyWeeks(1), not just a weekday and an hour. Google documents nearMinute as approximate, within plus or minus fifteen minutes. Check the project timezone; do not sell this as guaranteed arrival at 09:00.

Before relying on any workflow, verify a known total, preview without sending, send to one controlled recipient, and then observe a background execution separately. Check both the execution record and the received message. Finally, prove that you can disable the schedule. A manual send, an installed trigger and an inbox receipt are different pieces of evidence; none substitutes for all the others.