Description
Overview
This RSS feed notification automation workflow enables periodic monitoring and filtered dispatch of new feed items to Telegram. This event-driven analysis pipeline detects fresh RSS entries based on their publication timestamp, ensuring that only novel content triggers Telegram notifications. Designed for users seeking automated content updates, it employs a Cron trigger node to schedule feed reads and an IF node for conditional filtering.
Key Benefits
- Automates periodic RSS feed reading with configurable interval scheduling.
- Filters new RSS items using precise timestamp comparison to avoid duplicate notifications.
- Delivers formatted messages to Telegram chats with dynamic content from the RSS feed.
- Maintains state by tracking the latest read publication date for deterministic processing.
Product Overview
This automation workflow initiates with a Cron node triggering every minute, which starts the RSS feed reading from a specified URL. Each feed item includes key metadata such as title, link, and ISO 8601 publication date. The “Latest Read” function node accesses stored global state for the last processed item’s date, defaulting to June 1, 2021, if uninitialized. An IF node then evaluates whether each RSS item is newer than the stored date and verifies the title is non-empty. Items passing this dual condition proceed to update the stored latest read date to the newest item’s timestamp, ensuring future runs only consider subsequent entries. The Telegram node formats and sends notifications containing a fixed label, the item’s title, and link to a configured chat ID using authenticated API credentials. If no new items are detected, the workflow terminates silently via a NoOp node. The execution is synchronous from feed read to notification dispatch, with no data persistence beyond the static global variable and no explicit error handling mechanisms configured beyond platform defaults.
Features and Outcomes
Core Automation
This no-code integration pipeline processes RSS feed items by comparing publication timestamps against a tracked latest read date. It deterministically branches items based on freshness and title presence, enabling precise filtering before notification delivery.
- Single-pass evaluation of feed items against stored latest read timestamp.
- Conditional logic node ensures only new, valid entries proceed downstream.
- State persistence via static global data guarantees idempotent processing.
Integrations and Intake
The workflow integrates an RSS feed reader node to fetch XML feed items and a Telegram node for message dispatch. Authentication for Telegram requires API credentials, while the RSS feed URL must be specified. The intake expects standard RSS items with fields including title, link, and isoDate.
- RSS Feed Read node for periodic fetching of XML feed data.
- Telegram node authenticated via API key for message delivery.
- Cron node manages scheduled trigger every minute for continuous monitoring.
Outputs and Consumption
Output consists of formatted Telegram messages sent synchronously for each new RSS entry detected. Each message includes a label, the item’s title, and a clickable link. The workflow does not produce persistent output files or logs beyond Telegram message delivery.
- Telegram messages containing combined static label and dynamic feed content.
- Synchronous dispatch upon detection of new RSS items.
- No local data storage beyond the static latest read timestamp.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow is initiated by a Cron node configured to trigger every one minute, providing a time-based polling mechanism for the RSS feed. This ensures consistent, scheduled execution without external event dependency.
Step 2: Processing
The RSS Feed Read node fetches the feed XML from the configured URL and outputs items containing title, link, and isoDate fields. The Latest Read function node appends the stored latest read date from global static data to each item. Basic presence checks ensure titles are not empty before further processing.
Step 3: Analysis
The IF node applies two conditions: it compares the publication date of each RSS item to the stored latest read date, passing only newer items, and verifies that the title field is non-empty. This deterministic filtering prevents reprocessing of older or invalid entries.
Step 4: Delivery
For items passing the filter, the Write Latest Read function updates the global static data with the newest isoDate to maintain state. Subsequently, the Telegram node synchronously sends a formatted message for each new item, combining a fixed label with the item’s title and link. If no new items are found, the NoOp node terminates the workflow quietly.
Use Cases
Scenario 1
A news monitoring service needs to alert a Telegram channel about breaking articles. This automation workflow reads an RSS feed every minute, filters for only new articles based on publication date, and sends formatted notifications. The result is timely, consistent alerts without duplicate or outdated messages.
Scenario 2
A financial analysis team tracks currency fluctuation reports published via RSS. Using this RSS feed notification automation workflow, new reports are detected and immediately forwarded to their Telegram group. This ensures the team receives fresh data promptly for decision-making.
Scenario 3
A content aggregator wants to streamline updates from multiple sources into a single Telegram channel. By configuring this event-driven analysis pipeline with different RSS feed URLs, the workflow filters and pushes only the latest valid items, reducing manual checking and improving update reliability.
How to use
To deploy this workflow within n8n, configure the RSS Feed Read node with the desired feed URL. Set the Telegram node’s credentials with a valid API key and specify the target chat ID. Adjust the Cron node if a different polling interval is required. Once activated, the workflow runs automatically, sending Telegram messages for new feed entries. Users can monitor execution via n8n’s interface to verify message delivery and update the latest read timestamp. The output is immediate notification of fresh RSS content without duplicates, suitable for continuous live operation.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Manual feed checking, message formatting, and posting | Automated scheduled feed reading and conditional Telegram notification |
| Consistency | Variable due to human error and timing inconsistencies | Deterministic filtering ensures only new, valid items trigger messages |
| Scalability | Limited by manual monitoring capacity | Scales automatically with feed size and polling frequency |
| Maintenance | Requires continual manual effort and attention | Minimal maintenance after initial configuration, state persisted internally |
Technical Specifications
| Environment | n8n automation platform |
|---|---|
| Tools / APIs | RSS Feed Read, Telegram, Cron, Function, IF, NoOp nodes |
| Execution Model | Synchronous, event-driven workflow triggered by Cron |
| Input Formats | RSS XML feed with standard item fields (title, link, isoDate) |
| Output Formats | Telegram messages with formatted text content |
| Data Handling | Transient processing with static global data for latest read timestamp |
| Known Constraints | Requires valid RSS feed URL and Telegram API credentials |
| Credentials | Telegram API key for message sending |
Implementation Requirements
- Valid RSS feed URL configured in the RSS Feed Read node.
- Telegram API credentials and target chat ID properly set for the Telegram node.
- n8n instance with network access to both RSS feed source and Telegram API endpoints.
Configuration & Validation
- Set the RSS feed URL and verify it returns valid RSS XML with expected fields.
- Configure Telegram API credentials and chat ID, then test sending a message manually.
- Run the workflow manually or wait for a scheduled trigger to confirm new items produce Telegram notifications.
Data Provenance
- Trigger: Cron node initiating workflow every one minute.
- Input: RSS Feed Read node retrieving feed items with title, link, and isoDate.
- State management: Latest Read and Write Latest Read function nodes maintaining latest processed isoDate.
- Output: Telegram node sending formatted messages with label, title, and link fields.
FAQ
How is the RSS feed notification automation workflow triggered?
The workflow is triggered by a Cron node configured to execute every one minute, initiating scheduled RSS feed reads without external input.
Which tools or models does the orchestration pipeline use?
This event-driven analysis pipeline utilizes RSS Feed Read, IF conditional node, Function nodes for state management, and the Telegram node for delivery, orchestrated within n8n.
What does the response look like for client consumption?
The workflow produces Telegram messages containing a fixed label, the RSS item’s title, and a clickable link, delivered synchronously upon detection of new items.
Is any data persisted by the workflow?
Only transient state is persisted in n8n’s global static data to track the latest read publication date; no external databases or logs are maintained.
How are errors handled in this integration flow?
No explicit error handling nodes are configured; the workflow relies on n8n’s platform default error management and retries for node failures.
Conclusion
This RSS feed notification automation workflow provides a reliable mechanism to detect and forward new RSS content to Telegram channels, using timestamp-based filtering and state persistence to avoid duplicates. It supports continuous, automated monitoring with minimal manual intervention. A key constraint is the dependency on the availability and format consistency of the external RSS feed and Telegram API access. Overall, it offers a deterministic and scalable solution for real-time content alerting within n8n’s no-code integration environment.
Reviews
There are no reviews yet.