Start herebeginner~15 min
Automate a Weekly Report From Google Sheets to Slack or Email
Add a scheduled trigger in Zapier or Make that reads your Google Sheet every Friday, pulls the key numbers into a short message, and posts it to a Slack channel or emails it. No spreadsheet macros and no code. You build it once, pick the day and time, and the report sends itself from then on while you do other work.
Automate a Weekly Report From Google Sheets to Slack or Email
Add a scheduled trigger in Zapier or Make that reads your Google Sheet every Friday, pulls the key numbers into a short message, and posts it to a Slack channel or emails it. No spreadsheet macros and no code. You build it once, pick the day and time, and the report sends itself from then on while you do other work.
What you are building
A short report that writes and sends itself. Every Friday at 4pm (or any time you pick), an automation opens your Google Sheet, reads the week's key numbers, drops them into a tidy message, and posts it to a Slack channel or emails it to whoever needs it. You stop opening the sheet, copying figures, and pasting them into a message every week. You build it once in a no-code tool and then it runs on its own, on time, without you remembering to do it.
Step 1: Build a clean summary row in your sheet
The automation is only as tidy as the cells it reads. Make a tab called "Weekly Summary" with the handful of numbers that matter: revenue, new leads, tickets closed, whatever your team tracks. Use formulas like SUM or a pivot so each number totals the week automatically. Put them in fixed cells, for example revenue in B2 and leads in B3. Now the automation reads finished figures, and when you want to change what the report shows, you change this tab once instead of touching the automation.
Step 2: Add a scheduled trigger
Open Zapier or Make and start a new automation (a "Zap" in Zapier, a "scenario" in Make). For the first step, choose the built-in Schedule trigger and set it to run weekly on Friday at your chosen hour. This is the alarm clock. It does nothing but wake the automation up on time, every week, so the report fires whether or not anyone is at their desk. Pick a slot late enough that the day's numbers are in, but early enough that people read it before they log off.
Step 3: Read the numbers from Google Sheets
Add a Google Sheets step set to "Get Many Rows" or "Lookup Row" and connect your account once with the guided sign-in. Point it at your spreadsheet and the Weekly Summary tab. The automation now grabs the values from those fixed cells and holds them as fields you can reuse. Run a test on this step alone and confirm the real numbers show up. Seeing your actual revenue and lead count appear here is proof the hardest part, the connection, works before you build anything on top.
Step 4: Write the message and pick Slack or email
Add your final step. For Slack, choose "Send Channel Message" and pick the channel; for email, choose the Gmail or Outlook "Send Email" action. Write a short template and drop the sheet fields into it where the numbers go. Keep it skimmable, like: "Weekly numbers: Revenue 12,400. New leads 38. Tickets closed 61. Have a good weekend." One line per metric reads far better than a paragraph. Map each value to its cell field so the real figures fill in every Friday.
Step 5: Guard against empty or wrong weeks
Before you trust it, add one safety check. Insert a filter (Zapier) or a router with a condition (Make) that only lets the message send when the revenue cell actually has a value. That stops a blank report going out if the sheet was not updated. Send one manual test run and read the result as your team would. Fix the wording or the cell mapping, test again, then switch the automation on. From here it sends every week, on time, untouched.
A no-code rule of thumb
Let the spreadsheet do the math, and let the automation do the moving. Formulas in your Weekly Summary tab handle every calculation; the Zapier or Make steps only read finished numbers and deliver them. Keep that split and these workflows stay easy to fix and easy to grow. When you want a second report, you copy the automation, point it at a different summary row, and change the channel. If you would rather keep everything inside Google itself, a scheduled Apps Script can read the same tab and post it, though that path does involve a little code.
Try this now
Open your sheet and build the Weekly Summary tab first, even before you touch any automation tool. Put this week's revenue in one cell and this week's lead count in another, using a SUM formula so they total on their own. That single tidy tab is the foundation. Once those two numbers sit in fixed cells, wiring a Friday Slack or email message on top takes about ten minutes.
Try this now
Your turn: open zapier and build a clean summary row in your sheet. Just do step one now — the rest takes minutes. Save this guide to pick up where you left off.
FAQ
Do I need to know any code to build this?
No. Zapier and Make both let you pick a schedule, choose your Google Sheet, and drop the values into a Slack or email step by clicking through menus. The only typing you do is the wording of the message itself. If you later want the spreadsheet to crunch the numbers first, Google Sheets formulas handle that without code too.
Where should the report numbers come from in my sheet?
Point the automation at one summary row or a small set of named cells, not your raw data. Build a tab that already totals the week with formulas like SUM or a pivot, then have the automation read those finished figures. That keeps the message clean and means you change the layout in one place, not in the automation.
Slack or email, which should I pick?
Pick where the team already looks. A shared Slack channel is best for a number the whole team should see and react to; email suits a report that goes to a client or a manager who lives in their inbox. You can send to both by adding a second action step, and the numbers come from the same read either way.
What if the numbers are wrong or the sheet is empty that week?
Add a filter or condition step that checks the cell has a value before the message sends, so an empty week does not post a blank report. In Make you can also turn on error handling to alert you instead of failing silently. Always run one manual test and read the message before you trust it on a schedule.