n8n GitHub Release Alerts to Telegram via RSS Feed

Get notified on new GitHub releases—automatically sent to Telegram (hourly, grouped)

This n8n workflow watches one or more GitHub repository release feeds and sends a single grouped alert to your Telegram

What this workflow does

• Runs hourly using a schedule trigger to continuously monitor your repositories.
• Builds a feed list from your comma-separated watch list by converting each repository into its public releases.atom feed URL (supports owner/repo and full GitHub URLs).
• Fetches release entries from each repository’s public GitHub releases RSS/Atom feed, continuing even if one feed fails.
• Filters and detects new releases by excluding pre-releases unless enabled, then comparing entries to what was previously sent.
• Formats a grouped Telegram message with release title, date, notes excerpt, and a link.
• Stays within Telegram limits by splitting output to avoid exceeding Telegram’s message size limit.
• Prevents re-sends by remembering which release IDs were successfully sent in n8n workflow static data between runs.
• Sends alerts to Telegram using HTML parse mode, with link previews disabled.

Use cases

• Follow upstream updates for critical GitHub dependencies and engineering tools.
• Monitor releases for multiple SaaS components and notify your team in Telegram instantly.
• Keep operators informed of new versions without manually checking GitHub.

Technical details

• Scheduling: Schedule Trigger (runs every hour).
• Feed reading: RSS Feed Read (GitHub releases.atom URLs).
• Processing: Set and Code nodes to manage configuration, filtering, grouping, and message formatting.
• Messaging: Telegram node (HTML parse mode; link previews disabled).
• Persistence: n8n static data stores previously sent release IDs.
• Extras: Sticky Note for workflow documentation.

Setup (high level)

• Create a Telegram bot via @BotFather and add the bot token as Telegram credentials in the Telegram node.
• Provide your Telegram chat ID in the watch list configuration.
• Enter repositories in the watch list as owner/repo (or full GitHub URLs), and optionally enable pre-releases and adjust the release-notes excerpt length.
• Activate the workflow—seen release IDs are stored between runs.