Skip to main content

Logging checklist

Get a row per review into your sheet

Choose one receiver, then follow its group. The last group applies either way.

Receiver A: Apps Script web app
Receiver B: a middleware
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.

  • Problem 2

    Google Sheets has no webhook address

    There is no setting in a sheet that accepts a request from outside.

  • 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.

  • Problem 4

    We only wanted the numbers

    Building a log to count reviews is more plumbing than the question deserves.

  • Problem 5

    Webhooks are not on our plan

    Without the webhook, the sheet goes back to being filled by hand.

Apps Script or middleware

From Google’s Apps Script docs and Zapier’s webhook help, read on 2026-11-17.
PointApps Script web appMiddleware such as Zapier or Make
CostPart of your Google accountThe middleware’s own plan; Zapier’s webhook trigger is not on its Free plan
CodeA short script you maintainNone, mapping in a form
Changing columnsEdit the script and deploy againRemap the step
Workspace rulesSome admins block anonymous web app accessNeeds the middleware connected to your Google account

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.

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

  1. Web Apps, Google Apps Script documentation. Checked 2026-11-17.
  2. Class Sheet: appendRow, Google Apps Script reference. Checked 2026-11-17.
  3. Web app and API executable manifest resources (access levels), Google Apps Script documentation. Checked 2026-11-17.
  4. Trigger Zaps from webhooks, Zapier Help Center. Checked 2026-11-17.

Last updated 2026-11-17.