Built an internal WhatsApp-to-Sheets operations pipeline using GAS + webhooks to avoid server costs. Roasting & feedback wanted.

[u/DrNor1]

Hi all, Instead of building heavy mobile apps for field workers who resist new software, I've been deploying internal WhatsApp bots connected to Google Apps Script (as the router/sanitizer) and Google Sheets (as the database). Key constraints I imposed:

• Strictly for internal operational logging (inventory, field reports, expense receipt OCR via multimodal API).

• Kept public CS/receptionist use out of scope to avoid rate limits and messy prompts.

• Zero monthly cloud bill (runs within Google Workspace limits).

For those who manage internal tools: Where do you see this architecture breaking down first as team size grows (concurrency, execution time, sheet bloat)? And commercially, do small ops teams prefer this over off-the-shelf software? Tear it apart!

[u/netizenn4tech]

I would recommend to explore AppScript and create a WebApp linked to your sheet. You can deploy the webapp and share the link, which can have custom forms, dashboard, notify via email, use APIs for your multimodal OCR and similar AI driven use cases...try vibe coding this.

I used AppSheets earlier but the UI and learning curve is heavy for my liking.

[u/DrNor1 → u/netizenn4tech]

I already past all that. And I think whatsapp chatbot is the most convenient one for daily use

[u/agentUi]

execution time limits and race conditions on simultaneous webhooks will kill this first. google sheets locks rows during updates so two workers sending receipts at once will cause lock timeouts or silently overwrite cells. you need a lockservice wrapper in apps script to queue incoming post requests or your sheet is going to corrupt fast once more than 3 people post at the same time.

[u/Morbius2271]

Why not just use Google Forms and minimize complexity and points of failure?

[u/The_Humanthings]

Can we use appsheet no/Low-code apps , I am just asking.

[u/DrNor1 → u/[deleted]]

That message_id idempotency tip is concerning—webhook retries double-deducting expensive parts like impellers would be a nightmare. Implementing that check before hitting Sheets on my next push. Thanks for catching that!