MAKE · TESTED WORKFLOW

How to Send Webhook Data to Google Sheets with Make

A practical, evidence-labeled walkthrough of one controlled workflow: receive a webhook, map its fields, add a Google Sheets row, and verify the execution.

Last verified: 2026-09-01 JST

EVIDENCE SUMMARY

TEST STATUSCOMPLETED

WHAT WE TESTEDWebhook → mapped fields → Sheets row

SYNTHETIC DATAYes · no customer data

NOT TESTEDHigh-volume or long-term reliability

What we tested

TESTED BY ORAVENDA Custom Webhook → mapped fields → Google Sheets Add a Row. The test used synthetic values only: name, email, source, and message. The destination sheet retained one canonical test row.

Test flow

Custom Webhook→Detect fields→Google Sheets: Add a Row→Execution check

ACTUAL TEST EVIDENCE

Verified screenshot to be added.No screenshot is shown here until privacy review is complete.

Setup process

Create a Custom Webhook and use Run once so Make can receive a sample payload.
Send one synthetic payload. Make must detect the incoming structure before the fields appear for mapping.
Connect Google Sheets. Google OAuth authorization is required.
Choose Add a Row, select the worksheet, and map the detected fields to the four destination columns.
Run once and inspect both module results and the execution history.

The important troubleshooting detail

TESTED BY ORAVENDA Mapping was not available until the webhook structure had been detected. Existing queued webhook data could be reused during Run once.

How to verify success

Check the Webhooks and Google Sheets Add a Row results, then independently inspect the sheet. In our run, the four mapped values produced a real row and the execution was shown as successful.

What the Free plan supported

OFFICIAL PRODUCT FACT Make's pricing page lists a $0 Free plan with 1,000 credits per month, two active scenarios, a 15-minute minimum interval, and 3,000+ apps. The controlled test cost USD 0; future usage may exceed Free limits.

What we did not test

UNVERIFIED / NOT TESTED This single synthetic run does not establish high-volume throughput, enterprise performance, complex branching, long-term reliability, or failure recovery.

This route matched our controlled test.

Use the evidence above to decide whether this workflow fits before you try it.

Affiliate link — Oravenda may earn a commission at no extra cost to you.

Try Make free →