Keep an eye on public web pages without doing daily checks. This setup watches a specific section of a page, logs each change, stores a copy in Google Drive, and sends a Gmail alert when something new appears. It is ideal for tracking terms of service, policy updates, or competitor pages.

Here is how it works. A scheduled trigger runs at the time you choose. The HTTP Request node loads the page using a real browser user agent, and the HTML node pulls only the section you want using a CSS selector. The content is cleaned and hashed so small layout shifts do not cause false alerts. If the hash is new, the flow saves a snapshot to Google Drive, writes a row in Google Sheets with the link and hash, and sends a Gmail summary with the page URL, date, and Drive link. Only new changes pass through, so you do not get spammed.

Getting started is simple. Set the URL in the Variables node and update the HTML selector so it targets the right element. Connect your Google accounts and choose your spreadsheet and Drive folder. Teams can cut manual checks and get a clear audit trail of what changed and when. Use it for compliance reviews, policy tracking, or monitoring key competitor pages.

• Schedule Trigger runs at set times so checks happen automatically.
• HTTP Request fetches the page with a real User Agent to reduce blocking.
• HTML extraction grabs only the section you care about using a CSS selector.
• Markdown node cleans HTML into stable text for reliable hashing.
• Crypto hashing detects real changes and ignores minor formatting shifts.
• Remove Duplicates passes only new hashes so repeat alerts are filtered out.
• Google Drive uploads a snapshot of the changed content for proof.
• Google Sheets appends a log entry with URL, hash, and the Drive link.
• Gmail sends a clear text email with the page URL, date, and snapshot link.
• Variables node stores the tracked URL in one place for quick updates.

• Reduce manual page checks from 60 minutes to 5 minutes per day
• Send alerts only when content actually changes to cut noise by over 90 percent
• Keep a full audit trail with a Drive snapshot and a row in Google Sheets
• Improve accuracy by hashing cleaned content instead of raw HTML
• Scale monitoring by duplicating the flow for more pages without extra effort

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Sheets, Google Drive and Gmail. See the Tools Required section above for links to create accounts with these services.
3. Open the Variables node and replace the sample URL with the page you want to track. Save the node.
4. Double click the HTTP Request node and confirm the User Agent header is present. If the site blocks requests, change the header value to another common browser string.
5. Open the HTML Extract node and update the CSS selector so it targets the exact element that holds the content you care about. Test with the Execute Node button to see the extracted value.
6. Connect Google Drive: double click the Google Drive node, choose Credential to connect with, click Create new credential, then follow the on screen steps to sign in with your Google account and approve access. Pick a folder for snapshots.
7. Connect Google Sheets: double click the Google Sheets node, choose Credential to connect with, click Create new credential, then follow the on screen steps. Select your spreadsheet and sheet. Confirm the columns map to website, hash, and gdrive.
8. Connect Gmail: double click the Gmail node, choose Credential to connect with, click Create new credential, then follow the on screen steps. Set the To address and review the subject and message placeholders.
9. Open the Schedule Trigger and set your timezone and run frequency. Daily at a set time works well for policy pages.
10. Check the Remove Duplicates node options. Confirm it is deduping by the hash field so only real changes pass through.
11. Run a test: click Execute Workflow. If no change is detected, the run will stop before email. To simulate a change, temporarily tweak the selector or track a page that you know has just updated.
12. Verify outputs: confirm a new file appears in your Google Drive folder, a new row is added in your Google Sheet, and a Gmail alert arrives with the Drive link and date.
13. Troubleshoot: if the site returns an error, try a different User Agent or remove cookies. If rows do not log, recheck the Sheets credential and selected sheet. If no email is sent, confirm the change reached the Gmail node by viewing the execution data.