Description
Overview
This change detection automation workflow monitors the Hacker News homepage by fetching its HTML content twice within a defined interval. This event-driven analysis pipeline is designed for users who require reliable detection of webpage updates and instant notification delivery without manual intervention, leveraging a scheduled cron trigger that initiates HTTP requests every five minutes.
Key Benefits
- Automates webpage content monitoring using scheduled HTTP requests every five minutes.
- Detects changes by comparing sequential HTML responses to identify content updates.
- Integrates Telegram notifications for immediate alerts upon change detection.
- Employs a wait period to ensure accurate differential comparison between page states.
Product Overview
This automation workflow initiates with a cron trigger set to execute every five minutes, prompting an initial HTTP GET request to the Hacker News homepage URL. The raw HTML response is captured as a string and followed by a deliberate pause of five minutes implemented by a wait node. After the wait, a second HTTP GET request fetches the current state of the same page. The workflow then enters a conditional logic node that evaluates whether the two HTML responses differ.
If the content matches exactly, indicating no change, the workflow routes to a no-operation node that terminates the process silently. If the content differs, the workflow triggers a Telegram node which sends a predefined message alerting the user to the detected change. This response model operates synchronously within each execution cycle, relying on native n8n nodes without additional error handling or persistence layers beyond platform defaults.
Features and Outcomes
Core Automation
This change detection orchestration pipeline takes sequential HTML snapshots of a target webpage and compares them using an IF node to determine content changes. The workflow uses HTTP Request nodes for data intake and a wait node to introduce a time delay for meaningful comparison.
- Single-pass evaluation with scheduled triggers every five minutes.
- Deterministic boolean condition to detect exact HTML content changes.
- Branching logic routes outputs to notification or no-op nodes based on comparison.
Integrations and Intake
The workflow integrates HTTP APIs to fetch webpage content and Telegram API for notifications. Authentication for Telegram uses pre-configured API credentials, while HTTP requests require no authentication. The incoming payloads are simple string responses containing full HTML content.
- HTTP Request nodes retrieve webpage HTML content for comparison.
- Telegram node dispatches alert messages using API key-based credentials.
- Cron node schedules periodic workflow execution without external input.
Outputs and Consumption
Outputs consist of either no action or a Telegram text message sent to a specified chat ID. The notification is dispatched asynchronously only upon detecting changes, while no output occurs if the webpage remains static.
- Telegram messages include a static alert text confirming detected changes.
- No-operation path silently terminates workflow if no changes are detected.
- Output formats adhere to plain text messaging via Telegram API.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow begins with a Cron node configured to trigger every five minutes, initiating the process automatically without manual input or external webhook calls.
Step 2: Processing
An HTTP Request node fetches the full HTML content of the Hacker News homepage as a string. Following this, a Wait node pauses execution for five minutes before the next HTTP request, allowing temporal gap for change detection. The workflow performs basic presence checks on responses but does not apply schema validation.
Step 3: Analysis
The workflow uses an IF node to perform a boolean comparison between the first and second HTTP request outputs. It compares the raw HTML strings directly to detect any difference. If the content is identical, it routes to a no-operation node; if different, it proceeds to trigger a notification node.
Step 4: Delivery
On detecting a change, the Telegram node sends a message with predefined text to a configured chat ID using stored Telegram API credentials. This notification dispatches asynchronously at the end of the workflow execution cycle.
Use Cases
Scenario 1
A developer wants to monitor the Hacker News homepage for updates without manual refreshes. This workflow automates content polling and delivers Telegram notifications only when changes occur, ensuring timely awareness of new posts or updates.
Scenario 2
An information analyst requires a consistent method to track webpage changes for research. The automation workflow provides deterministic detection of HTML content difference, reducing manual verification efforts and delivering alerts on actual content modifications.
Scenario 3
A system administrator needs to verify uptime and content stability of a key news site. By comparing sequential page snapshots and alerting upon differences, this orchestration pipeline enables proactive monitoring and rapid notification of unexpected changes.
How to use
Import the workflow into your n8n environment and ensure Telegram API credentials are configured with the appropriate chat ID. Enable the workflow to run live, which will trigger every five minutes as per the configured cron schedule. Expect automated HTTP requests fetching webpage content and conditional Telegram notifications sent only when changes are detected between two sequential page captures.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual page checks and notification dispatches. | Fully automated with scheduled triggers and conditional routing. |
| Consistency | Human error and inconsistent polling intervals. | Deterministic content comparison with fixed five-minute intervals. |
| Scalability | Limited by manual effort and attention span. | Scales automatically with no additional operational input. |
| Maintenance | Requires recurring manual monitoring and alerting. | Low maintenance relying on stable API endpoints and cron scheduling. |
Technical Specifications
| Environment | n8n automation platform |
|---|---|
| Tools / APIs | HTTP Request, Wait, IF, Telegram, Cron, NoOp nodes |
| Execution Model | Scheduled synchronous execution with conditional branching |
| Input Formats | HTTP GET responses as raw HTML strings |
| Output Formats | Telegram text messages, no-op silent termination |
| Data Handling | Transient in-memory processing; no data persistence |
| Known Constraints | Relies on continuous availability of external web and Telegram APIs |
| Credentials | Telegram API key-based authentication |
Implementation Requirements
- Active n8n environment with workflow import capability.
- Configured Telegram API credentials with valid chat ID for notifications.
- Unrestricted outbound network access to https://news.ycombinator.com and Telegram API endpoints.
Configuration & Validation
- Import the workflow into n8n and configure Telegram credentials with correct chat ID.
- Enable the workflow and verify the cron trigger initiates execution every five minutes.
- Confirm Telegram messages are received when changes occur on the monitored webpage.
Data Provenance
- Trigger node: Cron triggers workflow execution every five minutes.
- Data intake nodes: HTTP Request nodes fetch HTML content from Hacker News.
- Output node: Telegram node sends notification messages upon detected changes.
FAQ
How is the change detection automation workflow triggered?
The workflow is triggered by a Cron node set to run every five minutes, initiating the sequence of HTTP requests and comparison automatically without manual input.
Which tools or models does the orchestration pipeline use?
The workflow uses HTTP Request nodes to retrieve webpage content, a Wait node for timing control, an IF node for boolean comparison of page content changes, and a Telegram node for notification dispatch.
What does the response look like for client consumption?
The client receives a Telegram text message stating “Something got changed” whenever the workflow detects a difference between two sequential HTML page fetches.
Is any data persisted by the workflow?
No data is persisted; the workflow processes all HTML content transiently in memory and does not store any snapshots or logs beyond the current execution cycle.
How are errors handled in this integration flow?
The workflow relies on n8n’s default error handling without explicit retry or backoff logic configured in the nodes.
Conclusion
This change detection automation workflow provides a deterministic method for monitoring webpage content by comparing two fetched HTML snapshots spaced five minutes apart. It reliably notifies users through Telegram messages only when actual content differences are found, minimizing unnecessary alerts. The solution depends on the availability and consistency of external HTTP and Telegram APIs and does not persist any data between runs. This design ensures straightforward monitoring with minimal maintenance in a fully automated environment.
Reviews
There are no reviews yet.