How to Automate Business Reports to WhatsApp: A Setup Guide for Indian SMBs (2026)

67% of knowledge workers spend three or more hours every day on manual coordination tasks like pulling reports, copying numbers, and sending status updates (Quixy, 2024). That's a Monday morning not spent on customers. For Indian SMB founders, the daily revenue check, the weekly leads summary, and the Friday cash position review are all routine, all predictable, and all things a machine can do for you. This guide shows how to set them up so the report arrives on your WhatsApp before you've finished your chai.

What Do You Need to Build Report Automations?

The setup is lighter than most founders expect. You need three things: a Make account (the free plan covers one or two reports), WhatsApp Cloud API access through Meta's Developer Portal, and a data source such as Google Sheets, Zoho CRM, or Zoho Books. According to Make.com pricing, the Core plan at Rs 750/month includes Google Sheets, WhatsApp, and scheduled triggers, which covers every automation in this guide.

The four components of a report automation

• Make account: Free plan works for one to two reports running once a day. For five reports on different schedules, the Core plan at Rs 750/month is the right tier. It includes 5,000 operations per month, which is more than enough for daily and weekly scheduled runs.
• WhatsApp Cloud API access: Set up through Meta's Developer Portal at developers.facebook.com. You'll need a Meta Business Manager account and a phone number not already linked to a WhatsApp account. Approval takes two to four business days. Cost: Rs 0.35 to Rs 0.58 per business-initiated conversation in India (Make.com, 2025). Five daily reports to one founder costs roughly Rs 15 to Rs 25/month in API fees.
• Approved message templates: WhatsApp requires all outbound automated messages to use a pre-approved template. Meta reviews templates within 24 to 48 hours. You'll submit your report format as a template with variable placeholders like {{revenue}} and {{date}} that Make fills in at send time.
• Data source: Google Sheets (linked to your payment gateway or manual entry), Zoho CRM for leads data, or Zoho Books for outstanding invoices. All three have native Make modules - no API key setup needed.

Time investment: two to four hours per report, built once. After that, the report runs itself every day or every week without any input from you.

How Should You Format Report Messages for WhatsApp?

WhatsApp is not email. Messages that work beautifully in an email client look cluttered and hard to read on a phone screen. WhatsApp limits messages to approximately 1,000 characters before truncation, doesn't render HTML tables, and has its own rules for bold and italic text. Getting the format right is half the work.

WhatsApp message formatting rules

• Line breaks: Use in your Make text formatter to create line breaks. Each key metric should sit on its own line. Grouping five numbers into one paragraph makes them unreadable.
• Bold: Wrap text with *asterisks* for bold. Use it for section headers within the message, not for every data point.
• 5 to 7 data points maximum: If you include more than seven numbers, the recipient stops reading. Pick the metrics that require a decision or action. Everything else belongs in a dashboard, not a WhatsApp message.
• No tables: HTML or markdown tables don't render in WhatsApp. Use labelled lines instead: "Website: 12 leads" on one line, "Referral: 8 leads" on the next.
• Comparison line: Always include a "vs previous period" comparison where you can. "Revenue: Rs 84,000 (vs Rs 71,000 last week, +18%)" is more useful than just the number. Make's Math module handles the percentage calculation automatically.
• Emoji use: One emoji per section header helps with visual separation on small screens. Avoid emoji in formal contexts (reports to accountants, investor summaries).

Keep the total message under 800 characters to be safe. Write your template in a notes app first, count the characters including the variable placeholders, then submit it to Meta for approval. Shorter templates get approved faster.

Report 1: How to Automate a Daily Revenue Summary to WhatsApp

This is the report that most Indian founders check manually every evening. Revenue for the day, number of invoices raised, biggest payment received. Automating it takes two to three hours to build and then runs without you indefinitely. Google Sheets linked to your payment gateway, or even manually updated, is all you need as a data source.

Make scenario structure for daily revenue

1. Trigger: Scheduled - every day at 20:30 IST (15:00 UTC). Make uses UTC internally. IST is UTC+5:30, so 8:30 PM IST equals 15:00 UTC. Set this in the scheduler settings. See the timezone section below for the Make account setting you must change.
2. Google Sheets - Read Range: Pull today's revenue rows. Use a filter on the date column (match today's date using Make's formatDate function) to get only today's entries. Read columns: date, amount, customer name, invoice number.
3. Tools - Set Variable (Aggregator): Sum the amount column to get total revenue. Count rows for invoice count. Find the maximum amount for the top payment. Calculate the percentage change vs yesterday by reading the previous day's total from a summary sheet.
4. Tools - Format Text: Build the message string using line breaks. Example output: "Revenue: Rs 84,200 | Invoices: 11 | Top payment: Rs 18,500 from Mehta Traders | vs yesterday: +12%"
5. WhatsApp Cloud API - Send Template Message: Send to your number (or your finance manager's number) using the approved template. Map the text formatted in step 4 into the template's body variable.

[UNIQUE INSIGHT] The formatting step is where most tutorials stop too early. WhatsApp's template system requires you to define which parts of the message are fixed and which are variables before submission to Meta. If you try to send a free-form text message without a pre-approved template, the API returns a 400 error. Plan your template structure first, then build the Make scenario around it.

Time to build: two to three hours for the first time, including template submission and approval wait.

Report 2: How to Automate a Weekly Leads Summary to WhatsApp

Manual lead counting is a real time sink. 30 to 40% productivity increases in year one are common when SMBs automate coordination tasks like lead summaries (Grand View Research via Quixy, 2024). This scenario pulls last week's leads from Zoho CRM or a Google Sheets tracker, groups them by source, calculates a conversion rate, and sends the summary every Monday at 9 AM.

Make scenario structure for weekly leads

1. Trigger: Scheduled - every Monday at 09:00 IST (03:30 UTC).
2. Zoho CRM - Search Records (or Google Sheets - Search Rows): Filter by lead creation date: last 7 days. Return fields: lead source, status, created date. If using Google Sheets, filter the date column using Make's dateDifference function.
3. Tools - Aggregate (Count + Group By): Count total leads. Group by source (website, WhatsApp enquiry, referral, ads). Count converted leads (status = "Won") for conversion rate.
4. Tools - Format Text: Build the message with source breakdown on separate lines. Example: "Total leads: 34 | Website: 14 | WhatsApp: 12 | Referral: 8 | Conversion: 18%"
5. WhatsApp Cloud API - Send Template Message: Send to the founder's number.

Time to build: three to four hours, including setting up the Zoho CRM connection and mapping the aggregation correctly. Google Sheets version is faster at two to two-and-a-half hours.

Report 3: How to Automate a Cash Position and Outstanding Payments Report

Outstanding receivables are the silent cash flow problem for most Indian SMBs. This report pulls unpaid invoices older than 30 days from Zoho Books every Friday evening and sends the total outstanding and the three oldest invoices directly to the founder's WhatsApp. No more opening Zoho Books to check before the weekend.

Make scenario structure for outstanding payments

1. Trigger: Scheduled - every Friday at 18:00 IST (12:30 UTC).
2. Zoho Books - List Invoices: Filter by status = "Unpaid" and due date more than 30 days ago. Return fields: invoice number, customer name, amount, due date. Sort by due date ascending to surface the oldest first.
3. Tools - Aggregate: Sum the amount field across all returned invoices for the total outstanding figure. Limit to the first three records for the message body.
4. Tools - Format Text: Build the message. Example: "Outstanding (30+ days): Rs 2,14,500 | Oldest 3: Rs 48,000 - Rajan Exports (62 days) | Rs 31,000 - Gupta Auto Parts (54 days) | Rs 28,500 - Metro Supplies (47 days)"
5. WhatsApp Cloud API - Send Template Message: Send to founder's number.

[PERSONAL EXPERIENCE] Friday evening is the best send time for this report, not Monday morning. Founders review the numbers before the weekend, mentally flag which customers to call, and often make those calls the first thing Monday. The same report sent Monday morning gets buried under the day's tasks and rarely triggers action before Wednesday.

Time to build: two to three hours. Zoho Books connection in Make is straightforward and the invoice filter module has good documentation.

Report 4: How to Build a GST Filing Deadline Reminder

Missing a GST deadline costs Rs 50 per day per return under GSTR-3B rules, up to a maximum of Rs 5,000 (GST Portal, 2025). A WhatsApp reminder three days before each deadline costs under Rs 2 in API fees. This scenario uses Make's date calculation to send deadline alerts automatically to your accountant and yourself, covering all three main returns.

GST deadlines to automate

• GSTR-1: Due 11th of every month. Set reminder trigger: 8th of month at 10:00 IST.
• GSTR-3B: Due 20th of every month. Set reminder trigger: 17th of month at 10:00 IST.
• GSTR-9 (Annual): Due 31 December. Set reminder trigger: 20 December at 10:00 IST.

Make scenario structure for GST reminders

1. Trigger: Scheduled - specific dates each month. In Make, create three separate scheduled scenarios: one for the 8th, one for the 17th, one for 20 December. Set the interval to "Monthly" and the day accordingly.
2. Tools - Set Variable: Calculate days remaining to the deadline using Make's dateDifference function between today and the due date.
3. Tools - Format Text: Build the alert. Example: "GSTR-1 due on 11th - 3 days remaining. Late filing penalty: Rs 50/day (max Rs 5,000). Please confirm data is ready for filing."
4. WhatsApp Cloud API - Send Template Message: Send to both the accountant's number and the founder's number using two WhatsApp send modules in sequence.

Note: Composition scheme filers have different deadlines (quarterly GSTR-4). If your business is on the composition scheme, adjust the trigger dates to the 18th of April, July, October, and January.

Time to build: one to one-and-a-half hours. This is the simplest scenario in the guide because it doesn't need to read from an external data source.

Report 5: How to Automate a Weekly Team Performance Summary

88% of SMBs say automation helps them compete with larger companies (Gitnux, 2024). A weekly team summary sent every Friday afternoon is one of the clearest examples: the same data that used to require a team meeting can arrive on everyone's phone in under 60 seconds. This scenario reads from a shared Google Sheets task or sales tracker and sends a formatted summary to each team member individually.

Make scenario structure for team performance

1. Trigger: Scheduled - every Friday at 17:00 IST (11:30 UTC).
2. Google Sheets - Read Range: Pull all rows from this week's date range. Columns: team member name, tasks completed, tasks open, deals closed, revenue vs target. Use one sheet per week or a date column to filter rows.
3. Iterator + Router: Make's Iterator module loops through each team member row. The Router sends a personalised message to each person's phone number (stored in a separate "Team" sheet mapped by name).
4. Tools - Format Text: Build a personalised message. Example: "Weekly summary - Priya: Tasks done: 14 | Open: 3 | Deals closed: 2 | Target: Rs 80,000 | Actual: Rs 91,000 (+14%)"
5. WhatsApp Cloud API - Send Template Message: One send per team member, using the personalised text as the template variable.

WhatsApp's Cloud API does not natively support group messages from the API. You can't send one API call to a group. The workaround is individual messages to each team member using the Iterator + Router structure above. It uses slightly more operations in Make but it's the only compliant method.

Time to build: three to four hours. The Iterator and Router step adds complexity but Make's interface handles it without code.

How Do You Set the Correct Schedule and Timezone in Make?

Timezone errors are the single most common reason report automations fire at the wrong time. Make stores and displays all times in UTC by default. India Standard Time is UTC+5:30, so every scheduled time you set must be converted manually before you enter it into Make's scheduler. Forgetting this means your 8:30 PM revenue report arrives at 2 AM.

IST to UTC conversion for common report times

Account-level timezone setting in Make

Make also has an account-level timezone setting that affects date functions like today() and formatDate(). If this is set to UTC instead of Asia/Kolkata, date filters in your Google Sheets and Zoho modules will be off by 5.5 hours. Go to Make - Profile - Settings - Timezone and set it to Asia/Kolkata. Do this before building any scenarios, not after.

For month-end reports (e.g., last-day-of-month summaries), use Make's "Run once" trigger combined with a date calculation: lastDayOfMonth(now) returns the last day of the current month. Pair it with a scheduled trigger on the 28th that checks whether today is the last day and proceeds only if true.

What Are the Most Common Mistakes When Automating WhatsApp Reports?

Most report automation failures come from four predictable mistakes. None of them are hard to fix once you know what to look for, but they're invisible until the scenario crashes at 11 PM on a Tuesday and you wake up to a Make error notification.

The four mistakes to avoid

• Forgetting the IST/UTC conversion: Covered above. Always convert every schedule time to UTC before entering it in Make. Bookmark the conversion table in this guide or keep it in a notes app.
• Not handling empty data: If your Google Sheet has no entries for today (a Sunday, a public holiday), the Read Range module returns nothing. Make's default behaviour is to crash the scenario. Add an error handler after the Sheets module: if the result is empty, either skip with a "Break" directive or send a "No data today" message instead. This single step prevents most middle-of-night error alerts.
• Sending without opt-in records: WhatsApp's policy and India's TRAI guidelines both require that recipients have opted in to receive automated messages from your business. Sending automated reports to phone numbers that haven't opted in risks your WhatsApp Business Account being flagged or suspended. For internal reports (to yourself, your accountant, your team), a written consent record in your HR policy is sufficient. For customer-facing messages, you need an explicit opt-in at point of collection.
• Messages that are too long: WhatsApp truncates messages beyond approximately 1,000 characters with a "Read more" prompt. Recipients rarely tap it. Keep every report message under 800 characters. If you're including more data than fits, split it into two messages or trim to the five most actionable numbers.

Frequently Asked Questions

Can I send automated reports to a WhatsApp group?

WhatsApp's Cloud API does not support sending messages to group chats directly from the API. Groups are outside the API's scope by design. The practical workaround is to send individual messages to each group member using Make's Iterator module, which loops through a list of phone numbers and sends a personalised (or identical) message to each one. For a team of five, that's five API calls per report send, costing roughly Rs 2 to Rs 3 total in WhatsApp fees per week.

What data sources work for automated WhatsApp reports?

Make has native modules for Google Sheets, Zoho CRM, Zoho Books, HubSpot, Tally (via webhook), Razorpay (via webhook), and most major databases via HTTP request. For most Indian SMBs, Google Sheets is the easiest starting point because it requires no API key setup, just a Google account connection. Zoho CRM and Zoho Books both connect in under 10 minutes through Make's app library. Tally requires a third-party connector or a custom webhook bridge but is achievable for tech-comfortable founders.

How do I set the correct India timezone in Make?

Go to your Make account, click your profile icon in the top right, then select Settings. Find the Timezone field and change it from UTC to Asia/Kolkata. Save the setting. This affects how date functions like now(), today(), and formatDate() work inside your scenarios. After changing it, also update any scheduled trigger times you've already created, because existing schedules store the time as entered and don't automatically recalculate for the new timezone setting.

Where to Go From Here

These five reports cover the information most Indian SMB founders check manually every day and every week. Building them once returns roughly 9.5 hours per week, which compounds quickly. The first report to build is Report 1, the daily revenue summary. It's the simplest data pull, the most immediate payoff, and it gives you the WhatsApp template approval process experience you'll need for every report that follows.

If you want to understand the broader landscape of WhatsApp automation beyond scheduled reports, including lead response flows, payment confirmations, and appointment reminders, the WhatsApp Business automation workflows guide covers eight trigger-based automations with the same step-by-step format. For a comparison of Make, n8n, and Zapier with India-specific pricing, read the workflow automation tools guide for India.

If you'd rather have these scenarios built for you and connected to your existing tools, the reporting automation service covers setup, template approval, testing, and a handover call so you understand exactly what's running and why.