Keep your team informed the moment code changes. The flow watches many GitHub repositories at once and posts alerts to Slack and Telegram. It fits engineering and IT teams that want fast, clean updates without manual checks.

Under the hood, a manual test step registers webhooks on each repo you list. Split nodes loop through the repo list, while HTTP requests create or delete webhooks on GitHub. A webhook trigger then receives push and pull request events in real time. Messages are shaped with Set nodes and sent to Slack and Telegram for quick action.

Setup needs a GitHub token with the right scopes and a correct webhook URL that points to the production URL from the webhook trigger. Expect faster response times, fewer missed changes, and less context switching. Use it for release updates, on call alerts, or PR activity across many repos without polling.

• Manual trigger to register webhooks across all listed repositories for safe testing.
• Set nodes to define the repo list and to format clean alert messages.
• Split Out nodes to iterate through repositories for create and delete actions.
• HTTP requests to GitHub API to register, fetch, and delete repository webhooks.
• Webhook trigger to receive push and pull request events in real time.
• Slack node to post alerts to a chosen channel with clear text.
• Telegram node to send the same message to a chat for instant mobile alerts.
• Delete flow to remove all registered hooks when you change scope or clean up.
• Reusable header auth credential for GitHub so all API calls share one token.

• Reduce manual repo checks from 2 hours a week to 10 minutes by automating webhook setup and alerts.
• Automate 90 percent of monitoring work by routing push and pull request events to chat.
• Cut alert time from hours to seconds with real time webhooks instead of polling.
• Connect GitHub, Slack and Telegram so teams act faster with one stream of updates.
• Scale to many repositories without extra effort using list based iteration.
• Lower missed changes by sending the same update to two channels for better coverage.

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, Slack and Telegram. See the Tools Required section above for links to create accounts with these services.
3. In GitHub, create a personal access token with scopes admin:repo_hook and repo. Copy the token for later.
4. Open the Register Github Webhook node in n8n. In the Credential to connect with dropdown, click Create new credential. Choose Header Auth, set Name to Authorization and Value to Bearer YOUR_GITHUB_TOKEN. Save.
5. Repeat the same credential on Delete Github Webhook and Get Existing Hook nodes. The Accept and API version headers are already set in the nodes.
6. Open the Webhook Trigger node and copy the Production URL. In the Register Github Webhook node, ensure the webhook config url uses this Production URL.
7. Open the Repos to Monitor Set node. Add your repository URLs in the repos field using the standard https://github.com/owner/repo format.
8. Connect Slack: open the Notify Slack node, click Create new credential, then follow the on screen steps to authorize your workspace and pick the channel.
9. Connect Telegram: in the Telegram node, click Create new credential and paste your bot token. You can create a bot with BotFather and invite it to your chat.
10. Disable the Webhook Trigger node for registration. Click Test workflow to run the manual registration path. Confirm webhooks exist by running the Get Existing Hook node and checking the output.
11. Enable the Webhook Trigger node and activate the workflow. Push a commit or open a pull request on any listed repo. Verify that Slack and Telegram both receive the alert.
12. To clean up hooks, use the Repos to Monitor1 list, then run the Delete flow through the manual trigger.
13. Troubleshooting: If you get a 404 or 401 from GitHub, check token scopes and repo access. If no alerts arrive, confirm the webhook URL uses the Production URL and that your n8n instance is reachable from GitHub.