You can connect WhatsApp to Google Sheets using Meta’s WhatsApp Business Platform Cloud API and a Google Apps Script web app: Meta sends webhook events to the script, and the script writes selected data into a spreadsheet. Meta offers free test resources, so this can be free to prototype; it does not mean that production messaging or a third-party provider will be free. The setup below explains the architecture and preparation, but does not present unverified webhook code as production-ready.
What the integration does—and what “free” means
There is no built-in WhatsApp-to-Sheets switch established by the sources for this guide. The supported approach is to connect the official WhatsApp Business Platform, commonly called the Cloud API, to a web endpoint and use that endpoint to write chosen data to Sheets. Meta’s WhatsApp developer hub links to its getting-started materials and webhook resources.
As an Amazon Associate I earn from qualifying purchases.
The basic flow is:
- A WhatsApp event, such as an incoming message, is delivered to the webhook endpoint configured for your app.
- A deployed Google Apps Script web app receives the HTTP request.
- The script validates and parses the request, selects the fields you need, and writes them to a Google Sheet.
Meta promotes free test numbers, sample code, webhooks, and a sandbox for prototyping. That is different from a guarantee of free production messaging: WhatsApp Business Platform usage is subject to Meta’s current rate card and pricing rules. Check the WhatsApp Business Terms for the current terms. A provider may also charge its own fees.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose direct setup or a managed provider
You can manage the connection yourself or use a provider that documents an integration path. The available provider example is promotional documentation, not an independent comparison or evidence of endorsement.
#1 Best Overall
- hole punched
- high quality card stock
- 4 pages
- made in USA
- keyboard shortcuts
| Path | Control and effort | Cost and operational considerations |
|---|---|---|
| Meta Cloud API + your Apps Script and Sheet | You control the script and spreadsheet, but must implement and maintain the integration, including webhook checks and failure handling. | Meta offers free test resources; production API charges may apply under its current rate card. Apps Script quotas and your reliability requirements constrain the design. |
| Managed provider + Sheets integration example | A provider may supply integration guidance, but you still need to understand its setup, data handling, and support arrangements. | Provider fees or markups may apply in addition to any applicable Meta charges. See the provider’s own terms before choosing it. |
D-API documents an example using WhatsApp API, Google Sheets, and Apps Script: D-API’s integration guide. Its example does not establish reliability, endorsement, or current pricing.
Prepare the WhatsApp Business Platform account
Start with Meta’s current WhatsApp Business Platform API collection and linked Cloud API getting-started documentation. Follow the current instructions for the business portfolio, WhatsApp Business Account (WABA), phone number, app permissions, access token, and test setup. These requirements and token details can change, so use Meta’s live documentation rather than copying old tutorials.
Webhook intake and sending a message are separate tasks. For incoming events, Meta requires the app’s webhook to be configured and subscribed to the WABA. For outgoing messages, your code makes a separate authorized API request and must follow Meta’s current messaging rules. Do not assume that receiving an event automatically enables sending.
Rank #2
- hole punched
- high quality card stock
- 4 pages
- made in USA
- keyboard shortcuts
Prepare the Sheet and Apps Script web app
- Create the destination spreadsheet. Add a worksheet for the events you want to retain. Decide on a small, explicit column schema—for example, event time, sender identifier, message identifier, event type, and message text where appropriate. Avoid collecting fields you do not need.
- Open its bound Apps Script project. In the spreadsheet, use Extensions > Apps Script. A bound script can work with its parent spreadsheet, but you still need to select the intended worksheet and handle missing or unexpected fields in your code.
- Implement an HTTP handler. Google’s Web Apps | Apps Script documentation says: “A script needs to contain a
doGet(e)ordoPost(e)function that returns anHtmlOutputorTextOutputobject to be published as a web app.” POST request content is available through the event object. A handler is only the HTTP entry point; it does not by itself implement Meta’s verification, request authenticity checks, or safe event processing. - Deploy and review access settings. In Apps Script, choose Deploy > New deployment, select the web app deployment type, and review who can access it and whether it runs as you. The endpoint must be reachable for Meta’s webhook delivery, but public reachability is not a substitute for authenticating incoming requests. Confirm the deployment settings and security approach against current Meta and Google requirements before connecting a live account.
Configure webhook receipt without skipping verification
Meta’s setup includes webhook verification and subscription of the app to the WABA. The exact current challenge-response and POST authenticity/signature requirements must be confirmed in Meta’s current webhook documentation before you rely on a direct Apps Script endpoint. Google documents the Apps Script web-app handler and event object, but that alone does not establish that a given deployment can safely satisfy every Meta requirement.
Before using the direct endpoint for real traffic, verify that it can:
- Complete Meta’s current webhook verification challenge and return the required response.
- Authenticate POST deliveries using the current Meta requirements, rather than trusting any request that reaches the URL.
- Respond in the way Meta expects while recording or processing the event safely.
If the chosen Apps Script deployment cannot meet those requirements, use a verified middleware or server endpoint that can, then pass only the necessary validated data to Sheets. Do not publish a runnable integration as secure until these details have been checked against the current platform documentation.
Rank #3
Write selected events safely
Once the webhook has been verified, treat incoming JSON as untrusted input. Parse the payload, identify the event type and fields you intend to retain, and write those values to the correct worksheet. Plan for repeated delivery: store a stable event or message identifier and check whether it has already been processed before appending a row. This reduces duplicate records when events are retried.
- Handle missing, malformed, or unexpected fields without silently writing misleading rows.
- Keep message content and personal data to the minimum your workflow requires, and restrict access to the spreadsheet.
- Record processing failures in a way you can inspect, and define how failed events will be retried or reconciled.
- Keep access tokens out of publicly accessible code and spreadsheet cells. Use an appropriate private configuration mechanism and limit who can access the script project.
These are design recommendations; a webhook-to-Sheets script does not automatically provide idempotency, retries, or production-grade data controls.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Send WhatsApp messages from Google Sheets only if needed
Sending is an optional, separate flow. Apps Script’s UrlFetchApp can make outbound HTTP(S) requests, which gives a script the transport mechanism for calling an API. See Google’s UrlFetchApp reference. Your implementation must still use Meta’s current endpoint, authorization, permissions, and messaging rules, including any applicable template requirements.
Rank #4
![The Google Workspace Bible: [14 in 1] The Ultimate All-in-One Guide from Beginner to Advanced | Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite](https://m.media-amazon.com/images/I/41AWmhmGFuL._SL160_.jpg)
- The Google Workspace Bible: [14 in 1] The Ultimate All in One Guide from Beginner to Advanced Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite
- ABIS BOOK
Do not put a production access token in a shared sheet or public script. Protect credentials and make sure a row edit or spreadsheet trigger cannot accidentally send messages to unintended recipients. Sending API requests also does not remove any applicable Meta or provider charges.
Test the connection and check limits
Begin with Meta’s test resources rather than real customer traffic. Exercise webhook verification, a valid event, malformed input, repeated delivery, a failed sheet write, and any outbound message path you intend to use. Inspect Apps Script’s execution history and the API responses as you test; this guide does not establish that a specific code sample or account configuration has been tested.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsGoogle’s dynamic Apps Script quotas page listed URL Fetch limits of 20,000 calls per day for consumer accounts and 100,000 per day for Workspace accounts when accessed on October 5, 2026. Google can change quotas, and these figures are account-specific limits for URL Fetch—not a throughput guarantee for the complete integration. Recheck the current page and the limits of the other services your script uses.
When Apps Script and Sheets are no longer enough
A spreadsheet-backed script is most suitable when the data volume is modest and the workflow can tolerate a lightweight, owner-maintained bridge. Consider a server or managed integration if your requirements demand stronger control over request authentication, retries, monitoring, concurrency, data retention, or uptime. Compare expected event volume with current Apps Script quotas, and account for the ongoing work of maintaining tokens, webhook behavior, and platform changes.
Before moving traffic, decide who owns failures, how duplicate events are prevented, how records are recovered after an outage, and who can access message data. If those responsibilities cannot be met reliably with your chosen endpoint and script, keep Sheets as a reporting destination rather than the system responsible for receiving and processing every event.
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.
