What this workflow does
This workflow checks GitHub for open issues labeled “Bug” every 10 minutes.
It finds new or updated bugs from the last 30 minutes.
Then it filters issues to show only those with fewer than 5 comments.
Finally, it sends a Telegram message with the issue title and link.
This helps users get quick alerts about urgent bugs without manual checks.
Who should use this workflow
This workflow is for developers or project managers who track GitHub issues.
It suits users who want to save time and respond faster to new bug reports.
Anyone using Telegram for notifications can benefit.
Also, users who want to reduce noise by ignoring bugs with many comments.
Tools and services used
- n8n Automation Platform: Runs the workflow nodes and schedules automation.
- GitHub API: Fetches repository issues with specific filters.
- Telegram Bot API: Sends messages with issue alerts.
Using a personal access token for GitHub and bot token + chat ID for Telegram is needed.
Inputs, processing steps, and output
Inputs
- GitHub repository owner and name.
- Personal Access Token with repo permissions.
- Telegram bot token and user chat ID.
Processing Steps
- A Schedule Trigger runs every 10 minutes.
- GitHub node queries open issues labelled “Bug”, updated or created in last 30 minutes.
- Set node extracts only issue title, link, date, and comment count.
- Filter node passes issues with fewer than 5 comments.
- Telegram node sends a message with issue title and hyperlink.
Output
Telegram messages notify user about new bug issues needing attention.
This output improves bug tracking response time.
Beginner step-by-step: How to use this workflow in n8n
Step 1: Import the workflow
- Download the workflow file using the Download button on this page.
- Open your n8n editor.
- Use “Import from File” to load the workflow into n8n.
Step 2: Configure credentials
- Add GitHub Personal Access Token in the GitHub node credentials.
- Enter your Telegram bot token and user chat ID in the Telegram node.
- Update repository owner and name fields if needed.
Step 3: Test and activate
- Manually run the workflow once and check Telegram for messages.
- Fix any errors if messages do not arrive.
- Activate the workflow to run automatically every 10 minutes.
Follow self-host n8n if using your own server.
Possible issues and solutions
- GitHub node returns no issues: Check owner and repo names, confirm token has repo reading rights.
- Telegram does not send messages: Verify the bot token and chat ID are correct.
- Filter node behaves wrongly: Ensure comment count field is number and condition is set to < 5.
Customization ideas
- Change the label filter in GitHub node to monitor other issue types like “Enhancement”.
- Adjust comment threshold to notify on fewer or more discussed bugs.
- Add fields like assignee or milestone in the Set node for richer alerts.
- Replace Telegram node with Slack or Email nodes for different notification platforms.
- Change schedule trigger interval from every 10 minutes to other timings.
Summary
✓ Saves hours weekly by automating GitHub bug issue checks.
✓ Sends quick Telegram alerts for new important bugs.
✓ Filters out crowded bug discussions to reduce noise.
✓ Runs every 10 minutes to keep users updated near real-time.
✓ Easy to set up with simple credentials and minimal configuration.