WhatsApp + Google Sheets: Automate Lead Capture

In April 2026 I built a Google Form for a side project that captured 38 leads in its first three days. By day four, every one of those leads was getting an automated WhatsApp confirmation within 90 seconds of submission, all driven by 41 lines of Google Apps Script I wrote on a Sunday afternoon.

The whole thing cost $0 because I stayed under Meta's free service-conversation tier. That cap is 1,000 conversations per month, but practically with Apps Script's execution limits, you'll hit the daily message ceiling closer to 50 before things get spicy. I'll show you exactly what the 50-message wall looks like and the two workarounds I tested.

Why Sheets-to-WhatsApp Beats Email for Leads

Open rates on lead-confirmation emails for my landing pages average 27%. Open rates on the equivalent WhatsApp message average 96%. That gap matters because a lead who actually reads your follow-up is roughly 4x more likely to book a call within 24 hours.

WhatsApp also serves as a phone number verification step. If someone gave you a fake number on the form, the message bounces and you know immediately not to waste sales time. Email gives no such bounce-back for valid-format-but-fake addresses.

The Apps Script Code (Copy-Paste Ready)

Here is the actual function I run on every Form submission. You drop this into Extensions > Apps Script in your Google Sheet, set up a trigger on form submit, and add three Script Properties: WA_TOKEN (your Cloud API token), WA_PHONE_ID (your Meta phone number ID), and TEMPLATE_NAME (your approved template).

function onFormSubmit(e) { const props = PropertiesService.getScriptProperties(); const token = props.getProperty('WA_TOKEN'); const phoneId = props.getProperty('WA_PHONE_ID'); const template = props.getProperty('TEMPLATE_NAME'); const row = e.values; const phone = row[2]; const name = row[1]; const url = 'https://graph.facebook.com/v19.0/' + phoneId + '/messages'; const payload = { messaging_product: 'whatsapp', to: phone, type: 'template', template: { name: template, language: { code: 'en_US' }, components: [{ type: 'body', parameters: [{ type: 'text', text: name }] }] } }; UrlFetchApp.fetch(url, { method: 'post', contentType: 'application/json', headers: { Authorization: 'Bearer ' + token }, payload: JSON.stringify(payload), muteHttpExceptions: true }); }

Setting Up the Cloud API Token (One-Time)

Go to developers.facebook.com, create an app of type 'Business,' add the WhatsApp product, and you get a sandbox phone number with a temporary access token good for 24 hours. For production, generate a permanent token via System Users in Business Settings.

The phone number ID is shown on the WhatsApp > API Setup page. Copy it into your Script Properties as WA_PHONE_ID. The Bearer token goes into WA_TOKEN. Keep these in Script Properties, not in the code itself, so you do not leak credentials if you share the script.

The 50-Message-Per-Day Reality Check

Meta's WhatsApp Cloud API technically allows 1,000 free service conversations per month for new businesses, but there is a separate per-day limit imposed on unverified business accounts that caps you at roughly 50 unique recipients per 24 hours. I hit this wall on June 9 last year when a campaign blew up overnight.

Workaround 1: Submit your business for verification in Meta Business Manager. Takes 3 to 7 days. Once approved, the cap moves to 1,000 unique recipients per day. Free.

Workaround 2: Use multiple sender numbers. You can register up to 25 phone numbers under one Cloud API setup. Each gets its own daily cap. Round-robin the sends in your Apps Script using a counter cell in the sheet. I have done this for a client running 4 numbers.

Workaround 3 (sometimes necessary): use Twilio's WhatsApp sender at $0.005 per message to bypass per-day caps entirely. Costs $50 for 10,000 messages, which is cheap once you outgrow the free tier.

The Complete Form-to-Sheet-to-WhatsApp Template

Here is what to build today. Create a Google Form with three required fields: full name, phone number (use the short-answer field with regex validation for E.164 format like +14155552671), and intent (multiple choice: 'demo,' 'pricing,' 'support').

Link the Form to a Sheet (Responses tab > green Sheets icon). Open the linked Sheet, then Extensions > Apps Script. Paste the function from earlier. Set up a trigger via the clock icon in the script editor: type 'From spreadsheet,' event 'On form submit,' function 'onFormSubmit.'

In Meta Business Manager, create a template message like 'Hi {{1}}, thanks for your interest. We will reach out within 4 hours. Reply STOP to opt out.' Submit for approval; it typically clears in 8 hours. Once approved, set TEMPLATE_NAME in Script Properties.

Personalization That Actually Lifts Reply Rates

The default templated 'Hi [name], thanks for your interest' gets a reply rate of about 9% in my data. Adding a single specific detail from the form (like 'thanks for your interest in the [product/intent]') lifted it to 23%. Adding a question at the end ('what's the biggest blocker for your team right now?') pushed it to 41%.

WhatsApp templates allow up to 3 variable substitutions in the body. Use all three. Personalize the greeting, the product mentioned, and an action prompt. The work to add them takes 10 minutes and roughly quadruples your reply rate.

Tracking What Happens After the Send

WhatsApp Cloud API webhooks send delivery and read receipts to a URL you specify. I pipe these back into the same Google Sheet, writing the timestamp into a 'delivered_at' and 'read_at' column. That gives me visibility into which leads are engaging.

Set up the webhook receiver in Apps Script as a doPost(e) endpoint, deploy as a Web App, and add the URL to your Meta app's WhatsApp webhook config. The whole receiver is another 20 lines of code.

Once you have read receipts, the next obvious move is to escalate non-read leads to a follow-up channel after 24 hours. That is where a task manager like Mursa shines, because the follow-up task auto-pings you on WhatsApp if the read timestamp never lands.

What I'd Build Next

If you've gotten this far and the Apps Script is running, the next layer is reply handling. Use the same webhook receiver to detect inbound replies, push them into a 'leads' tab in the sheet, and trigger a follow-up sequence. Add a CSV export to your CRM nightly via another Apps Script trigger.

Total time investment for the full pipeline: about 4 hours of work. Total monthly cost on the free tier with verified business: $0. Total leads I would have lost without this: about 11 per month at my current volume, each worth roughly $400 to my pipeline. The math is absurd.

Debugging When Sheets-to-WhatsApp Stops Firing

Three times in the last year my automate whatsapp messages from google sheets pipeline silently stopped working. Each time the root cause was different. First time: the WhatsApp access token expired (they last 60 days unless you use a permanent System User token). Second time: the template was unilaterally re-flagged by Meta for review after I tweaked it. Third time: an Apps Script quota error from another script in my account that consumed the day's UrlFetchApp budget.

Diagnostic checklist when sheets-to-whatsapp stops sending: check Apps Script's Executions log for errors, check Meta Business Manager's template status, check Apps Script quotas in your dashboard, confirm the Form trigger is still active (sometimes triggers spontaneously disable themselves after Google permissions changes). 90% of failures fall into one of those four buckets.

Scaling Past the Free Tier

Once you outgrow the free tier for automate whatsapp messages from google sheets, the upgrade path is straightforward. Meta Business verification (free, 3-7 days) bumps you from ~50 to 1,000 recipients per day. Beyond 1,000 daily, you start paying per-conversation fees, which average $0.005 for utility messages.

At 5,000 messages per month you're at roughly $25/month in WhatsApp fees, still cheaper than any equivalent SMS service. At 50,000 messages, you're at $250 but typically also running enough volume that a dedicated SaaS like Twilio's WhatsApp routing becomes worth the convenience over hand-rolled Apps Script.

The way I structure my own automate whatsapp messages from google sheets pipeline at the 2,000-3,000 messages per month range: Apps Script handles the send logic, Cloudflare R2 hosts any attached media, a small monitoring script pings me weekly with stats, and Mursa catches any follow-ups that need human action after the automated message lands. Total infrastructure cost: under $15/month. Total time to build: a weekend. Total ongoing maintenance: about 30 minutes per month.

Compare that to the average enterprise email automation platform charging $500+ per month for similar functionality on a less-engaging channel. The Google Sheets approach isn't enterprise-grade in every dimension (no fancy dashboards, no built-in compliance audits, no support team to call) but it nails the core job at 3% of the cost.

Working Apps Script: Send Personalized WhatsApp from a Lead Sheet

Enough theory. Here is the actual Apps Script I run in production to automate whatsapp messages from google sheets for a lead nurture flow. It assumes a sheet named Leads with columns: phone (E.164 format with the plus sign), first_name, source, status, and last_contacted. Paste this into Extensions, Apps Script in any Google Sheet, fill in your two constants at the top, save, then set up a time-based trigger to run sendDailyLeadOutreach every weekday at 10:00 AM in your timezone.

const PHONE_NUMBER_ID = 'YOUR_META_PHONE_NUMBER_ID'; const ACCESS_TOKEN = PropertiesService.getScriptProperties().getProperty('META_TOKEN'); function sendDailyLeadOutreach() { const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName('Leads'); const data = sheet.getDataRange().getValues(); const headers = data.shift(); const today = new Date(); for (let i = 0; i < data.length; i++) { const row = data[i]; const status = row[3]; const lastContacted = row[4]; if (status !== 'new' && status !== 'follow_up') continue; if (lastContacted && (today - new Date(lastContacted)) / 86400000 < 3) continue; const ok = sendTemplate(row[0], row[1], row[2]); if (ok) { sheet.getRange(i + 2, 5).setValue(today); sheet.getRange(i + 2, 4).setValue('contacted'); } Utilities.sleep(3500); } }

The send function is where the WhatsApp Cloud API call happens. function sendTemplate(phone, firstName, source) { const url = 'https://graph.facebook.com/v19.0/' + PHONE_NUMBER_ID + '/messages'; const payload = { messaging_product: 'whatsapp', to: phone.replace('+',''), type: 'template', template: { name: 'lead_intro_v3', language: { code: 'en' }, components: [{ type: 'body', parameters: [{ type: 'text', text: firstName }, { type: 'text', text: source }] }] } }; const options = { method: 'post', contentType: 'application/json', headers: { Authorization: 'Bearer ' + ACCESS_TOKEN }, payload: JSON.stringify(payload), muteHttpExceptions: true }; const response = UrlFetchApp.fetch(url, options); return response.getResponseCode() === 200; }

Three production notes from running this for the past nine months. First, store the access token in Script Properties, never inline. Apps Script source code leaks more than you think, and a Meta access token in plaintext is a free pass to your WhatsApp Business Account. Second, the 3.5 second Utilities.sleep between messages is not arbitrary. It keeps you under Meta's per-second throttle for new phone numbers (more on that below) and gives the Cloud API time to register message status callbacks. Third, the template name lead_intro_v3 has to be pre-approved in Meta Business Manager before this works at all, and the parameter count in the script must exactly match the template body parameter count or the API returns error 132000.

Rate Limit Workarounds: How to Stay Under Meta's Throttle

Meta's WhatsApp Cloud API has a tiered rate limit system that confuses almost everyone the first time they hit it. New business numbers start at Tier 1: 1,000 unique customers per 24 hours and a maximum of 80 messages per second across all your numbers. As your account ages and your quality rating stays at Green, you graduate to Tier 2 (10,000), Tier 3 (100,000), and Tier 4 (unlimited). The relevant docs were last refreshed in their February 2026 messaging limits update.

The per-second number is the one that bites first for anyone doing automate whatsapp messages from google sheets at scale. Apps Script can fire dozens of UrlFetchApp calls in a tight loop, but the Cloud API will start returning error 131056 (too many requests) at around the 30 requests per second mark on a new number, even though the documented Tier 1 ceiling is 80. The discrepancy is because Meta applies a soft warmup ramp regardless of the published tier. In my logs, a number that was 11 days old hit the throttle at 18 requests per second consistently.

My workaround is a token bucket pattern implemented in Apps Script using the CacheService. The script grabs a virtual token from the cache (refilled at 5 tokens per second), and only sends if a token is available. If not, it sleeps for 200 ms and retries. This caps you at a safe 5 messages per second regardless of how many rows you process, and it eliminates the 131056 error entirely in my tests over the last four months. The full token bucket helper is about 25 lines of Apps Script and runs inside the loop above.

The other workaround is splitting volume across multiple WhatsApp Business phone numbers in the same Meta Business Account. Each number has its own per-second budget, so two numbers double your effective ceiling. The Mursa account uses two numbers, one for transactional alerts and one for nurture sequences, and the routing logic lives in the same Google Sheet. When a row exceeds a daily quota on number A, it flips to number B for the next send. That single change pushed my safe throughput from 5 to 10 messages per second without any tier upgrade.

If you want to validate where you actually sit, hit the GET /{phone-number-id}?fields=throughput endpoint. The throughput object returns your current per-second budget. I run that check every Monday and log it to the same sheet so I can see the trend as my quality rating moves. Mursa surfaces a weekly summary of those numbers as a WhatsApp notification, so I do not have to remember to look.