Google Sheets log
Log New Testimonials in Google Sheets
A spreadsheet cannot listen for anything on its own. Something has to receive the request StoryProof sends for each new review (from Pro) and add the row. That something is either a short Apps Script attached to the sheet, or a middleware that already knows how to write to Sheets.
- Apps Script receiver or middleware, side by side
- Columns chosen from a real delivery
- Deployment settings that let the request in
Logging checklist
Get a row per review into your sheet
Choose one receiver, then follow its group. The last group applies either way.
The checklist runs in your browser and keeps nothing.
The problem, solved
Why the review spreadsheet is always behind
- Problem 1
Someone copies reviews into the sheet once a month
By reporting day half of them are missing and the rest have typos from retyping.
How StoryProof solves it
From Pro, each new review is sent out as it arrives, so a receiver can write the row without anyone copying.
- Problem 2
Google Sheets has no webhook address
There is no setting in a sheet that accepts a request from outside.
How StoryProof solves it
A doPost function deployed as an Apps Script web app gives the sheet an address, or a middleware does it for you. The StoryProof webhook points there.
- Problem 3
The sheet mixes approved and unapproved reviews
A row is written on arrival, before anyone has decided whether the review is fit to use.
How StoryProof solves it
Treat the sheet as an intake log. Nothing goes public until it is approved in StoryProof, and tags there mark the ones cleared for campaigns.
- Problem 4
We only wanted the numbers
Building a log to count reviews is more plumbing than the question deserves.
How StoryProof solves it
If counts and trends are the goal, the analytics dashboard included on every plan may answer it without a sheet.
- Problem 5
Webhooks are not on our plan
Without the webhook, the sheet goes back to being filled by hand.
How StoryProof solves it
The in-app alert, on every plan, at least tells the person who keeps the sheet that a review has landed.
Apps Script or middleware
In StoryProof
Start logging
Step 1 of 4
Prepare the sheet
One tab for the log, a frozen header row, and nothing else on that tab so appended rows land cleanly.
Step 2 of 4
Create the receiver
Deploy the doPost web app or create the middleware catch step, and copy its URL.
Step 3 of 4
Connect StoryProof
Add the URL where your StoryProof settings list webhooks, then submit one review through your own collection link.
Step 4 of 4
Fix the columns from the test row
Look at what arrived and name the headers after those fields. Do not guess fields you have not seen.
Before you start
Limits worth knowing
No Google Sheets connector
StoryProof is not described here as writing to Sheets itself. The webhook reaches a script or a middleware that does.
Column names depend on the delivery
This page does not list what the webhook contains. Build headers from a real test.
A log, not a moderation queue
Rows arrive before approval. Approve and tag in StoryProof, where the decision counts.
Written from vendor docs
The Google and middleware steps follow their documentation as of 2026-11-17 and were not run against a live sheet.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can the sheet send reviews back into StoryProof?
This page goes one way only. For moving existing reviews into StoryProof, see the CSV import guide.
What if my company blocks anonymous access to Apps Script?
Use a middleware instead. It receives the webhook on its own address and writes to the sheet through its Google connection.
Should email addresses go in the sheet?
Only if the delivery contains them and the people with access to the sheet need them. Leave the column out otherwise.
How do I spot a missed review?
Compare the sheet with what StoryProof shows now and then. A received-time column makes long gaps obvious.
Still have a question? Ask the StoryProof team or book a demo.
Keep a complete review log without retyping
Collect with StoryProof and let the webhook add each new review to your sheet.
Sources
- Web Apps, Google Apps Script documentation. Checked 2026-11-17.
- Class Sheet: appendRow, Google Apps Script reference. Checked 2026-11-17.
- Web app and API executable manifest resources (access levels), Google Apps Script documentation. Checked 2026-11-17.
- Trigger Zaps from webhooks, Zapier Help Center. Checked 2026-11-17.
Last updated 2026-11-17.