This workflow follows the RSS Feed Read → Telegram recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"nodes": [
{
"name": "RSS Feed Read",
"type": "n8n-nodes-base.rssFeedRead",
"position": [
420,
-20
],
"parameters": {
"url": "={{$node[\"SplitInBatches\"].json[\"url\"]}}"
},
"typeVersion": 1
},
{
"name": "SplitInBatches",
"type": "n8n-nodes-base.splitInBatches",
"position": [
200,
-20
],
"parameters": {
"options": {},
"batchSize": 1
},
"typeVersion": 1
},
{
"name": "Cron",
"type": "n8n-nodes-base.cron",
"position": [
-240,
-20
],
"parameters": {
"triggerTimes": {
"item": [
{
"mode": "everyX",
"unit": "minutes",
"value": 10
}
]
}
},
"typeVersion": 1
},
{
"name": "only get new RSS",
"type": "n8n-nodes-base.function",
"position": [
640,
-20
],
"parameters": {
"functionCode": "const staticData = getWorkflowStaticData('global');\nconst newRSSIds = items.map(item => item.json[\"isoDate\"]);\nconst oldRSSIds = staticData.oldRSSIds; \n\nif (!oldRSSIds) {\n staticData.oldRSSIds = newRSSIds;\n return items;\n}\n\n\nconst actualNewRSSIds = newRSSIds.filter((id) => !oldRSSIds.includes(id));\nconst actualNewRSS = items.filter((data) => actualNewRSSIds.includes(data.json['isoDate']));\nstaticData.oldRSSIds = [...actualNewRSSIds, ...oldRSSIds];\n\nreturn actualNewRSS;\n"
},
"typeVersion": 1
},
{
"name": "Telegram_IT",
"type": "n8n-nodes-base.telegram",
"position": [
1220,
460
],
"parameters": {
"text": "={{$json[\"title\"]}}\n{{$json[\"link\"]}}",
"chatId": "TelegramID",
"additionalFields": {}
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
},
{
"name": "Telegram_Security",
"type": "n8n-nodes-base.telegram",
"position": [
1220,
220
],
"parameters": {
"text": "={{$json[\"title\"]}}\n{{$json[\"link\"]}}",
"chatId": "TelegramID",
"additionalFields": {}
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
},
{
"name": "RSS Source",
"type": "n8n-nodes-base.function",
"position": [
-20,
-20
],
"parameters": {
"functionCode": "return [\n {\n json: {\n url: 'https://feeds.feedburner.com/UnikosHardware',\n }\n },\n {\n json: {\n url: 'http://www.ithome.com.tw/rss.php',\n }\n },\n {\n json: {\n url: 'http://feeds.feedburner.com/playpc',\n }\n },\n {\n json: {\n url: 'https://lab.ocf.tw/feed/',\n }\n },\n {\n json: {\n url: 'https://techcommunity.microsoft.com/plugins/custom/microsoft/o365/custom-blog-rss?tid=3754543230341459569&board=microsoft_365blog',\n }\n }\n];"
},
"typeVersion": 1
},
{
"name": "Telegram_M365",
"type": "n8n-nodes-base.telegram",
"position": [
1220,
-40
],
"parameters": {
"text": "={{$json[\"title\"]}}\n{{$json[\"link\"]}}",
"chatId": "TelegramID",
"additionalFields": {}
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
},
{
"name": "IF-2",
"type": "n8n-nodes-base.if",
"position": [
880,
240
],
"parameters": {
"conditions": {
"string": [
{
"value1": "={{$json[\"title\"]}}",
"value2": "\u8cc7\u5b89|\u8cc7\u8a0a\u5b89\u5168|\u5b89\u5168|\u5916\u6d29|\u76e3\u63a7|\u5a01\u8105|\u6f0f\u6d1e|\u5c01\u9396|\u4fee\u88dc|\u653b\u64ca|\u5165\u4fb5|\u500b\u8cc7|\u96b1\u79c1|\u79c1\u5bc6|\u9a19|\u793e\u4ea4\u5de5\u7a0b|\u91e3\u9b5a|\u99ed|Security|security|Secure|secure",
"operation": "regex"
}
]
},
"combineOperation": "any"
},
"typeVersion": 1
},
{
"name": "IF-1",
"type": "n8n-nodes-base.if",
"position": [
880,
-20
],
"parameters": {
"conditions": {
"string": [
{
"value1": "={{$json[\"link\"]}}",
"value2": "techcommunity.microsoft.com",
"operation": "contains"
}
]
}
},
"typeVersion": 1
},
{
"name": "Clear Function",
"type": "n8n-nodes-base.function",
"position": [
-20,
-180
],
"parameters": {
"functionCode": "// Get the global workflow static data\nconst staticData = getWorkflowStaticData('global');\n// Update its data\nstaticData.oldRSSIds = new Date().getTime();\n// Delete data\ndelete staticData.oldRSSIds;\n\nreturn [\n {\n json: {}\n }\n]"
},
"typeVersion": 1
}
],
"connections": {
"Cron": {
"main": [
[
{
"node": "RSS Source",
"type": "main",
"index": 0
}
]
]
},
"IF-1": {
"main": [
[
{
"node": "Telegram_M365",
"type": "main",
"index": 0
}
],
[
{
"node": "IF-2",
"type": "main",
"index": 0
}
]
]
},
"IF-2": {
"main": [
[
{
"node": "Telegram_Security",
"type": "main",
"index": 0
}
],
[
{
"node": "Telegram_IT",
"type": "main",
"index": 0
}
]
]
},
"RSS Source": {
"main": [
[
{
"node": "SplitInBatches",
"type": "main",
"index": 0
}
]
]
},
"RSS Feed Read": {
"main": [
[
{
"node": "SplitInBatches",
"type": "main",
"index": 0
},
{
"node": "only get new RSS",
"type": "main",
"index": 0
}
]
]
},
"SplitInBatches": {
"main": [
[
{
"node": "RSS Feed Read",
"type": "main",
"index": 0
}
]
]
},
"only get new RSS": {
"main": [
[
{
"node": "IF-1",
"type": "main",
"index": 0
}
]
]
}
}
}
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
telegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
How this works
Stay effortlessly informed on the latest news from your favourite sources by automating the delivery of RSS feed updates directly to your Telegram chats, saving time on manual checks and ensuring you never miss important stories. This workflow suits content curators, journalists, or anyone monitoring multiple feeds like tech blogs or industry newsletters, pulling in fresh articles and sending tailored notifications. The key step involves reading from various RSS sources with the rssFeedRead node, then filtering for new items before dispatching them via Telegram channels for seamless distribution.
Use this workflow when you need regular, automated summaries from diverse RSS feeds without constant app switching, particularly for scheduled daily or hourly updates to keep teams aligned. Avoid it for real-time breaking news demands, as the cron trigger introduces slight delays, or if your feeds require complex parsing beyond basic titles and links. Common variations include adding email alerts alongside Telegram or customising messages with specific keywords for targeted filtering.
About this workflow
Get Data From Multiple Rss Feeds To Telegram. Uses rssFeedRead, splitInBatches, telegram. Scheduled trigger; 11 nodes.
Source: https://github.com/Zie619/n8n-workflows — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
GNCA AI News Pipeline. Uses rssFeedRead, httpRequest, telegram, errorTrigger. Scheduled trigger; 31 nodes.
GNCA AI News Pipeline. Uses rssFeedRead, httpRequest, telegram, errorTrigger. Scheduled trigger; 29 nodes.
Graceful Content Sparks — RSS → Notion (n8n)
rss-telegram. Uses splitInBatches, telegram, rssFeedRead, manualTrigger. Scheduled trigger; 18 nodes.
This workflow gets latest RSS from different RSS Sources and categorizes them with conditional.