Skip to content

Website Change Alerts to Google Sheets: A Change Log Setup

Log every AyeWatch website change as a row in Google Sheets. Send the signed webhook to Make, Zapier or n8n, map six fields and keep a dated history of what a page changed.

By AyeWatch Team4 min read

Short answer: To log website changes in Google Sheets, send AyeWatch's signed webhook to Make, Zapier or n8n and have it add one row per alert. AyeWatch has no Google Sheets connection of its own, and a Google Apps Script endpoint is a poor receiver. Webhooks need a paid plan.

What belongs in a change log sheet

A sheet works well as a history: you can sort by date, filter by monitor and see how often a page moves. Six columns cover what AyeWatch sends. This is a made-up alert in the shape described in the webhook docs:

{
  "topic_id": 4471,
  "topic_name": "https://fernhillhardware.example/power-tools",
  "update_id": 70215,
  "headline": "Fernhill Hardware cuts the 18V drill kit to $129",
  "content": "The power tools page lists the FH-18 drill kit at $129, down from $159. The impact driver kit is unchanged at $149.",
  "created_at": "2026-11-27T11:02:00Z",
  "evidence": [
    { "quote": "FH-18 drill kit $129.00", "source_url": "https://fernhillhardware.example/power-tools" }
  ]
}

Sample rule: Alert me when Fernhill Hardware changes the price of a cordless drill or impact driver kit on its power tools page. Ignore stock labels and banner text.

The row for that alert has the time, the page, the headline, the summary, the source link and the update ID. The webhook carries AyeWatch's summary and supporting quotes. It does not attach a copy of the page.

Why a bare Apps Script endpoint falls short

It is tempting to paste a Google Apps Script web app URL into AyeWatch and skip the middle tool. Two things get in the way. A doPost handler receives the request body but not the request headers, so it cannot read X-AyeWatch-Signature and cannot check who sent the request. Apps Script web apps also commonly answer a POST with a 302 redirect. The AyeWatch docs ask for a 2xx reply and AyeWatch does not follow redirects, so the delivery counts as failed and is retried, up to 10 attempts. A retry can write the same row again.

A receiver tool avoids both problems.

Three receivers that can write the row

  • Make: a scenario that starts with the Webhooks module's Custom webhook trigger and ends with the Google Sheets module's Add a Row action. See the Make guide.
  • Zapier: a Zap that starts with Webhooks by Zapier, event Catch Hook, and ends with Google Sheets, action Create Spreadsheet Row. Catch Hook is a paid Zapier feature. See the Zapier guide.
  • n8n: a Webhook node followed by a Google Sheets node set to Append Row. See the n8n guide.

All three show a sample of the incoming data after the first delivery arrives, and you map fields from that sample. Trigger a real update first, then build the mapping, because the field list is built from what the tool has seen.

Keep retries from adding duplicate rows

AyeWatch's docs say a delivery may be attempted more than once, so treat a repeated update_id as the same alert. Put update_id in its own column. If a duplicate slips in, select the column in Sheets and use Data, then Data cleanup, then Remove duplicates. n8n's Google Sheets node also offers an Append or Update Row operation, which updates a row that already exists instead of adding one.

Make and Zapier answer the request themselves, so AyeWatch normally sees a 2xx at once and has nothing to retry.

When a spreadsheet is the wrong place

  • You need to be told, not to look back. A sheet is a log. Push and the in-app feed come with every plan, and Slack and email come with paid plans.
  • High volume. A busy account adds rows every day, and a spreadsheet has a cell limit. Start a new tab or file each quarter, or write to a database.
  • You need the whole page. The row holds a summary and quotes, not a snapshot of the page.
  • Pages behind a login. AyeWatch reads public pages and cannot sign in.

Cost and effort

AyeWatch Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode. Every plan starts with a 7-day free trial. Most checks use 1 credit. Google Sheets is free with a Google account. Make, Zapier and n8n each have their own plans and limits, so check their pricing pages before you count on a free tier.

Build the change log in six steps

  1. Create a sheet with six headers in row 1: Detected, Monitor, Headline, Summary, Source, Update ID.
  2. In Make, Zapier or n8n, start a new workflow with the webhook trigger and copy its URL.
  3. Create the monitor in AyeWatch and write the rule. Then open Notification settings, Webhook, paste the URL and select Save Webhook.
  4. Wait for the first real update so the tool captures a sample. Make has a Run once button that waits for one delivery.
  5. Add the Google Sheets step and map each field to its column, using the table below.
  6. Turn the workflow on and leave a header row frozen, so the log stays readable as it grows.
Sheet columnAyeWatch fieldNote
Detectedcreated_atISO 8601 timestamp, for example 2026-11-27T11:02:00Z
Monitortopic_nameThe page URL for a web page monitor
HeadlineheadlineShort summary of the change. Can be missing, so leave the cell blank.
SummarycontentFull text of the update. Set the column to clip text.
Sourcefirst item of evidence, source_urlEvidence can be missing on some updates
Update IDupdate_idUse it to spot repeated deliveries

Start a monitor in under a minute

Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.

Try it free for 7 days

The bottom line

Make the sheet with its six headers today and build the receiver in the tool you already use. Let one monitor fill it for a week, then decide whether the log earns a second monitor.

FAQ

Can AyeWatch send alerts straight to Google Sheets?

No. AyeWatch has no Google Sheets connection of its own. Send its signed webhook to Make, Zapier or n8n and add a row from there.

Can I use a Google Apps Script web app as the webhook URL?

It is a poor fit. The doPost handler cannot read request headers, so it cannot check the AyeWatch signature, and Apps Script web apps commonly reply with a redirect that AyeWatch counts as a failed delivery.

How do I avoid duplicate rows?

Store update_id in a column. AyeWatch's docs say a delivery may be attempted more than once, and the same alert keeps the same update_id.

Which AyeWatch plan sends to a webhook?

Paid plans do. AyeWatch Pro is $9/mo and Pro+ is $19/mo, and every plan starts with a 7-day free trial.

Does the sheet get every change on the page?

It gets every update AyeWatch reports for the monitor, as a summary with quotes. AyeWatch sends a webhook only when it detects new content, not on every check.

website change alerts to google sheetslog website changes in google sheetsgoogle sheets website change trackermonitor a website and add a row to google sheets

Related articles