Monitor website changes with PolyDoc screenshots and email alerts
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every 6 hours). Along the way it connects Polydoc (community).
How it runs
Trigger: On a schedule (every 6 hours).
- Settings (Edit Fields (Set)): sets 1 field: url
- Fetch page (HTTP Request): calls an HTTP API (GET)
- Detect change (Code): runs custom JavaScript code
- Changed? (If): checks a condition and branches into true / false
- Screenshot page (Poly Doc): screenshot
- Email screenshot (Send Email): sends an email over SMTP
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-polydoc is verified or supports 3.0 (used in Screenshot page).
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Poly Doc
n8n-nodes-polydoc.polyDoc - Send Email
n8n-nodes-base.emailSend - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick Overview This workflow checks a website URL every 6 hours, detects content changes by hashing the normalized HTML, and when a change is found it uses PolyDoc to capture a full-page screenshot and emails the PNG as an attachment. How it works 1. Runs…