MAKE · TESTED WORKFLOW
Know whether your incoming data reached the right spreadsheet fields
A received request is not the same as a completed row. Start with the expected result, inspect the bounded test below, and decide whether this setup fits your handoff.
Can you check the result before relying on it?
In a separate September 9, 2026 test, three synthetic requests each produced one source value in Google Sheets. We checked each destination value exactly once. The Free account balance fell from 996 to 990 credits across those three manually processed runs. This two-module webhook-to-Sheets test does not establish how a failed or repeated request will behave; recovery and duplicate handling remain untested.
If fields do not appear, the recorded setup required a sample to be detected before mapping. Google authorization is also required. Use a separate synthetic record and inspect the destination; retain your current handoff while evaluating.
Article reviewed and updated: 2026-09-10 JST
EVIDENCE SUMMARY
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. In the earlier September 1 setup demonstration, the destination sheet retained one canonical test row. That demonstration used name, email, source and message. It is separate from the September 9 credit test above, which used three requests and wrote one source value per request.
Earlier setup demonstration: September 1
ACTUAL TEST EVIDENCE
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 Neither the earlier single-run setup demonstration nor the separate September 9 three-run credit test establishes 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.
Related reading
Estimate this route with the Make.com Credits Calculator, compare Make vs Zapier, check whether Make Free is enough, review the Pabbly Connect vs Make comparison, or read the Oravenda methodology.