Get quick updates on important GitHub bugs without opening your browser. Every ten minutes, new or active issues are checked and the right alerts are sent to Telegram. It helps engineering and product teams act faster and cut noise.

A scheduled check looks for open issues with a Bug label from the last 30 minutes. The flow pulls each issue, keeps key fields like title, link, created time, and comment count, then filters by comment activity so you only see items people are discussing. A short Telegram message sends the title and a direct link to your user or group chat. This keeps attention on issues that matter and reduces false alarms.

Setup needs a GitHub token, a Telegram bot token, and a chat ID. You can change the repo owner and name, the label list, the lookback window, and the comment threshold. Expect faster triage, fewer missed items, and less time spent checking GitHub. Great for on call alerts, PM watchlists, and QA handoffs.

• Scheduled polling runs every 10 minutes to keep updates fresh.
• GitHub issues are fetched with filters for open state, Bug label, and the last 30 minutes.
• Key fields are mapped, including title, link, created time, and comment count.
• A comment threshold filter sends only issues with real activity.
• Telegram messages include the issue title and a clickable link to the issue.
• Simple repo owner and name inputs make targeting your repository easy.

• Reduce manual checks from 30 minutes per day to 2 minutes
• Cut bug response time by 50 percent with instant alerts
• Lower noise by up to 70 percent by alerting only on active issues
• Connect GitHub and Telegram for fast, direct updates
• Stay current with checks every 10 minutes across the day

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with GitHub and Telegram. See the Tools Required section above for links to create accounts with these services.
3. Open the GitHub node, click Credential to connect with, choose Create new credential, then follow the on screen steps. Use a Personal Access Token with repo scope if your repository is private.
4. Create a Telegram bot using BotFather and copy the bot token. In the Telegram node, create a new Telegram credential and paste the token. Start a chat with your bot so it can message you.
5. In the Telegram node, set Chat ID to your username or numeric chat ID. If sending to a group, add the bot to the group and use the group chat ID. Set Parse Mode to Markdown so the link renders.
6. In the GitHub node, set the Owner and Repository fields. Keep the filters to state open and labels Bug, or change the label to match your process.
7. Keep the since field as the last 30 minutes lookback or change the time window to match your alerting needs.
8. Open the Set node and confirm the fields you need are mapped, such as title, html_url, created_at, and comments.
9. Open the Filter node and set the condition so comments is greater than your threshold, for example greater than 0 to catch active issues.
10. Click Execute Workflow to test. Create a test issue with the Bug label and add a comment. Confirm a Telegram message arrives with the title and link.
11. Enable the workflow and let it run on schedule. Check execution logs in n8n if you do not see messages.
12. Troubleshoot by checking repo permissions, label names, chat ID format, and that you have started the bot chat. If alerts seem quiet, widen the time window or lower the comment threshold.