Google Sheets webhook in Make.com
Updated 2026-08-01
People often search "Google Sheets webhook" when they want a sheet change to start a Make.com scenario — or when a custom webhook should write into Sheets. Those are two different setups. This page separates trigger vs write, and what to check when nothing moves.
Two common setups
Sheet → Make: a Google Sheets trigger (for example watching new or updated rows) or an intermediary that calls a Make custom webhook when the sheet changes. Make must be listening on a live scenario with the correct trigger module.
Make → Sheet: a webhook or other trigger feeds Make, then an Add/Update a row module writes to Sheets. Failures here are often mapping (BundleValidationError / DataError), not "webhook dead".
When nothing arrives
Confirm the scenario is on, the webhook URL (if any) matches the sender, and you are not looking at an old scenario copy.
If the webhook queue has items but Sheets modules fail later, fix the module error — the receive side may already work.
Paste the exact execution error into the free diagnosis when Make shows a named error on the Sheets or HTTP step.
Paste the error for a sourced diagnosis
If you still have the execution log, use the free tool — Make's docs only, every claim linked, or an honest refusal when coverage is missing.
Example you can try: Google Sheets webhook in Make is not receiving new rows. The scenario trigger stays empty after editing the sheet.
Official Make documentation
FAQ
Is a Sheets "Watch" the same as a custom webhook?
No. Watch modules poll or use Google-side change detection depending on the module. A custom webhook is a URL Make exposes for an external POST. Pick the pattern that matches how your sheet change is signaled.
Related guides
- Make.com webhook not receiving data
- BundleValidationError on Google Sheets in Make.com
- DataError in Make.com
Eviverse is independent and not affiliated with Make. These guides are original explanations with links to Make's public Help Center — not republished documentation.