Monitoring Appointment Pages with n8n: Respectful, Robust Approaches
Monitoring an appointment booking page from n8n is feasible without aggressive scraping-use conditional HTTP requests, content hashing, and cautious scheduling to detect real changes while respecting site limits. The right pattern reduces the risk of being blocked and avoids legal or ethical problems.
Recommended technical approach
Start with lightweight HTTP checks: use n8n's HTTP Request node with conditional headers like If-None-Match and If-Modified-Since to rely on server-side caching (ETag/Last-Modified). When those headers aren't provided, fetch the minimal HTML fragment needed and compute a content hash to detect meaningful changes. Only escalate to a headless browser (Playwright) when the page is heavily client-side rendered or when you must interact to reveal availability.
How to avoid being blocked
Respect robots.txt and the site's terms of service. Implement conservative polling intervals (e.g., every few minutes or longer depending on appointment volatility) and backoff logic for HTTP 429 or other server errors. Randomize request intervals slightly, reuse connections, and include a clear User-Agent. If you manage many monitors, consolidate requests through a single respectful proxy and stay within published rate limits.
Workflow pattern in n8n
1. Schedule Trigger node -> 2. HTTP Request (conditional headers) -> 3. Function node to compute content hash and compare with last known value stored in n8n's credentials or external DB -> 4. If changed, parse and extract slots/status -> 5. Notify via Telegram/Email. Add retry/backoff branches and logging for auditability.
Governance and ethical considerations
Document your monitoring policy, have legal review for government sites, and favor APIs if available. If you detect frequent blocking, reach out to the site owner for an API or permission. That keeps your operation sustainable and reduces the risk of enforcement or service disruption.
Original Source
n8n Community