receive schedule events and get hash of contents and notify of change
Configured with Crypto, Gmail, Google Drive, Google Sheets, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Messaging
- Data store
- Web / API
- Files / media
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Get Hash of Contents | Transform | Crypto | See node parameters |
| Notify of Change | Messaging | Gmail | See node parameters |
| Markdown | Transform | Markdown | See node parameters |
| Variables | Transform | Edit Fields | See node parameters |
| Only New Hashes | Transform | Remove Duplicates | removeItemsSeenInPreviousExecutions |
| Log Record | Data store | Google Sheets | append |
| Fetch Webpage | Web / API | HTTP Request | See node parameters |
| Extract Contents | Transform | Html | extractHtmlContent |
| Take a Snapshot | Files / media | Google Drive | createFromText |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2googleDriveOAuth2ApigoogleSheetsOAuth2Api
Workflow notes
1. Fetch a Webpage Contents
1. Fetch a Webpage Contents
2. Use Hashing to Detect Changes
2. Use Hashing to Detect Changes
3. Notify when Changes Occur
3. Notify when Changes Occur
Try it out
Try it out
This n8n template can monitor and detect changes to a webpage's contents and notify you only when a change occurs.
Great to keep an eye on and track publicly available documents such as company TOS, government policy or competitor pages.
How it works
- A scheduled trigger is used so we can run everyday to automate this process.
- A website page is then fetched with the HTTP request node and the contents we want to track are extracted using the HTML node.
- To detect changes, we generate a hash on the contents with the cryptography node and compare it with previously seen hashes using the "remove duplicates" node. If the hash was seen before, the workflow stops here.
- Finally, when new changes are detected a copy of the contents are uploaded to Google Drive and a logged into a Google sheet. A notification email can also be sent if action is required.
How to use
- Update the URL you want to track in the node named "variables" and ensure the HTML node has updated selectors to get the content you want.
- Ensure the timezone is set correctly when using the Scheduled Trigger node.
Need Help?
receive schedule events and get hash of contents and notify of change
receive schedule events and get hash of contents and notify of change
Purpose and structure
This folder contains the receive schedule events and get hash of contents and notify of change workflow. Its executable nodes use crypto, gmail, googleDrive, googleSheets, html, httpRequest, markdown, removeDuplicates, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/0817_Schedule_Removeduplicates_Create_Webhook.json MIT; preserve source notices.