Log Incoming Webhook Requests to a Google Doc and Alert on WhatsApp
Turns each inbound webhook payload into a formatted Google Docs record and pings the responsible person on WhatsApp with the document details.
Use this templateWhy use it
Something is posting data at you — a form tool, a payment provider, a partner's system, an internal script — and it disappears the moment it arrives. When a customer says they submitted something and nobody acted on it, you have no record to check: no timestamp, no payload, nothing you can show a teammate. Debugging means asking the sender to replay the request, and by then the lead has gone cold or the failed charge has aged a week. The person who should have reacted first didn't know anything came in at all.
How it works
- 1An inbound request lands on a dedicated URL you can hand to any service that posts data. Whatever JSON or form fields it carries are captured in full, so nothing is lost even if no one is watching at that moment.
- 2Google Docs creates a new document holding that payload, laid out as a readable record instead of a raw blob — so you end up with a dated, searchable trail in Drive rather than a log file only a developer can open.
- 3WhatsApp, sent through WhatsScale, pings the person responsible with the details of the document just created, so they see the request arrived and can open the record straight from their phone.
What it connects
- Webhook
- Google docs
- WhatsScale
Questions
What kind of service can send data to this?
Anything that can make an HTTP request to a URL: form builders, payment providers, CRMs, monitoring tools, partner systems, or your own scripts. If it offers a webhook or callback field, paste the trigger URL in there.
Does it create one document per request, or append to a single running log?
Each incoming request creates its own new Google Doc. That keeps individual payloads easy to link to and share, and it means a burst of traffic never causes two writes to collide in one file.
What happens if the payload has fields I do not care about?
Edit the document body in the Google Docs step so it only pulls the fields you want. The webhook still receives everything, you just decide what gets written into the record and what is ignored.
Can more than one person get the WhatsApp alert?
The template sends to a single recipient as configured. To notify several people, duplicate the WhatsApp step for each number, or point it at a WhatsApp group so the whole team sees the same notice.
What if a lot of requests arrive at once?
Each request is handled as its own run, so a spike means more documents and more messages rather than lost data. If the volume gets noisy, add a condition before the WhatsApp step so only payloads that matter trigger an alert.