You can connect WhatsApp messages to Google Sheets with Meta’s WhatsApp Business Platform Cloud API, a Google Apps Script web app, and a spreadsheet. The basic bridge can be prototyped with Meta’s free test resources and Google Apps Script, but that does not make production messaging or a third-party provider free. The integration also requires webhook verification and security work; the architecture below is not a tested, production-ready recipe.
How the integration works—and what “free” means
There is no built-in WhatsApp-to-Sheets switch established by the available documentation. Instead, Meta sends WhatsApp webhook events to an endpoint you configure. A deployed Apps Script web app can receive HTTP requests and write selected event data into a Google Sheet. For outbound messages, Apps Script can make HTTP requests to Meta’s API; sending messages is a separate flow from receiving webhook events.
Meta’s WhatsApp developer hub offers free test resources, including test numbers, sample code, webhooks, and a sandbox. Those resources can help you prototype. Meta’s WhatsApp Business terms state that API use is billed according to the current rate card and pricing rules. Production charges may apply, and an intermediary may charge its own fees. Check current terms before launching; do not assume that test access means free production use.
Choose a connection route
| Route | What you manage | Trade-offs |
|---|---|---|
| Direct Meta Cloud API plus Apps Script and Sheets | You configure the Meta account and API, Apps Script endpoint, Sheet, webhook handling, and operational safeguards. | More control and no required integration provider, but you own implementation, security, retries, and maintenance. Meta API charges may apply. |
| Managed provider | A provider supplies a WhatsApp API service or integration example; the exact responsibilities depend on its offering. | May reduce setup work, but can add provider fees or markups. Verify its current webhook, reliability, security, and pricing details. A provider’s example is not independent evidence of reliability or Meta endorsement. |
For example, D-API documents an Apps Script and Google Sheets integration example. Treat it as provider documentation, not an independent comparison or a guarantee that the approach meets your requirements.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- hole punched
- high quality card stock
- 4 pages
- made in USA
- keyboard shortcuts
What you need before setting it up
- A Google account with access to Google Sheets and Apps Script.
- A Meta developer setup and the WhatsApp Business Account and phone-number configuration required by Meta’s current Cloud API onboarding.
- A destination spreadsheet and a clear decision about which message or status fields you need to retain.
- A plan for webhook verification, request authenticity, duplicate events, failures, access control, and token storage.
Meta’s current WhatsApp Business Platform API collection is the reference for setup requirements, credentials, permissions, webhook subscription, and messaging rules. Follow its current instructions rather than relying on copied token lifetimes or permission lists, which can change.
Prepare the Google Sheet and Apps Script
1. Create a destination tab and columns
In a new or existing spreadsheet, create a worksheet such as Messages. Choose columns based on the fields you actually need—for example, event time, sender identifier, message identifier, message type, and text where applicable. Store only necessary information, and consider whether message content belongs in a broadly accessible spreadsheet.
2. Open the bound Apps Script project
From the spreadsheet, select Extensions > Apps Script. A script bound to the spreadsheet can work with that file, but the web app still needs deliberate deployment and access settings. Do not put production access tokens in a public Sheet or in code that others can view.
3. Implement an HTTP handler and deploy it
Apps Script web apps receive requests through doGet(e) or doPost(e). Google states: “A script needs to contain a doGet(e) or doPost(e) function that returns an HtmlOutput or TextOutput object to be published as a web app.” See Google’s Web Apps | Apps Script documentation for request events, responses, and deployment. Choose deployment access settings that allow the intended service to reach the endpoint without exposing spreadsheet data or credentials unnecessarily.
Rank #3
- Mastering Google Sheets: A Step by Step Handbook for Beginners to Simplify Data Analysis, Boost Productivity, and Unlock Your Full Spreadsheet Potential
- ABIS BOOK
This describes the Apps Script capability, not complete runnable integration code. Before publishing or deploying a webhook implementation, confirm that its GET verification challenge and POST authenticity/signature checks satisfy Meta’s current requirements. The documentation cited here does not establish that a directly deployed Apps Script endpoint safely satisfies every current Meta requirement; if it cannot, use a verified middleware or server endpoint.
Configure webhook intake and write events safely
In Meta’s setup, configure the webhook callback endpoint and subscribe the app to the relevant WhatsApp Business Account so events can be delivered. Follow the current Meta API collection for the subscription and verification flow. Do not treat a publicly reachable Apps Script URL as sufficient proof that requests are authentic.
After verification is settled, have the handler parse the incoming JSON, select only the fields the Sheet needs, and append or update rows. Plan for repeated deliveries: use an event or message identifier to detect duplicates rather than assuming each request arrives once. Decide how to record malformed payloads and temporary failures, and how to retry without creating duplicate rows. These are design recommendations; the sources cited here do not validate a particular implementation.
Send WhatsApp messages from Google Sheets
Sending is optional and separate from logging incoming events. Apps Script’s UrlFetchApp can make outbound HTTP(S) requests, which can be used to call the Cloud API. Google documents this service in its UrlFetchApp reference. Your request must follow Meta’s current authorization, recipient, template, and messaging rules; consult the Meta API collection before implementing it.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Best Value
- hole punched
- high quality card stock
- 4 pages
- made in USA
- keyboard shortcuts
Keep access tokens out of public code, shared spreadsheets, and logs. Decide how credentials will be stored and who can access the Apps Script project. Do not assume a message can be sent merely because a row exists in the Sheet; the API request and applicable Meta rules still govern delivery.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the flow and diagnose problems
- Start with Meta’s test resources. Use the current test number and sandbox instructions in Meta’s developer hub, rather than a production recipient.
- Check each boundary separately. Confirm that Meta recognizes the webhook configuration, the endpoint handles verification, a test event reaches Apps Script, and the expected fields land in the intended worksheet.
- Inspect Apps Script executions. Google’s Apps Script interface provides execution monitoring; review failures and response behavior while testing. Consult the current quotas documentation if requests fail or volume grows.
- Test duplicates and errors deliberately. Confirm how the implementation handles a repeated event, invalid JSON, an API rejection, and a temporary failure. A successful single test does not demonstrate reliable delivery or production readiness.
Check Apps Script quotas before relying on it
Google’s dynamic quotas page lists URL Fetch limits of 20,000 calls per day for consumer accounts and 100,000 calls per day for Workspace accounts, as shown on the page accessed October 5, 2026. These are account-dependent product limits, not a throughput guarantee for this integration, and Google may change them. URL Fetch is only one constraint: your script’s execution behavior, webhook traffic, retries, and operational needs also matter.
When to move beyond Apps Script
Apps Script can be a practical low-cost bridge for a prototype or a modest workflow when its access controls, quotas, and operating model fit. Consider a dedicated server or managed integration when you need stronger control over request validation, sustained volume, dependable retries, detailed monitoring, or stricter data-handling controls. Compare the expected workload and security requirements with the maintenance you are prepared to own; a provider reduces some implementation work only if its specific offering meets those needs and its fees are acceptable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
