Stop checking GitHub by hand for every project you follow. This setup watches a list of repos each day and posts a clear note in Slack when a new release appears, so the team never misses a change. It fits engineering, DevOps, and product teams that need quick and reliable release news.

On a daily schedule, n8n starts the run automatically without anyone clicking a button. A Code step holds the repo list and n8n loops through each record, so you can track many projects at once with one flow. An HTTP request calls the GitHub latest release endpoint, an If check guards against repeats, and then a Slack node sends the release name plus a short preview of the notes to your channel with clean formatting. People see the update in one place, plan upgrades sooner, and avoid scanning multiple sites.

You only need a Slack workspace and access to the GitHub repos you want to track, with an optional GitHub token for higher rate limits. Add or remove repos in the Code node, pick the Slack channel, and choose the time that fits your working hours. Expect less manual work, faster awareness, and fewer surprises when upstream tools ship new versions.

• Daily schedule starts the run at the time you choose.
• Code node stores an editable list of org and repo pairs.
• HTTP Request pulls the latest release from the GitHub API.
• If node filters only new releases before alerting the team.
• Slack node posts a formatted message with release name and a short notes preview.
• Handles multiple repos by looping through each item from the Code node.
• Canvas notes remind where to add repos and how to customize the Slack text.

• Reduce manual checks from 30 minutes per day to under 2 minutes
• Automate monitoring for many repos in one run
• Send timely alerts to the right Slack channel
• Cut missed release risk by 80%
• Connect GitHub and Slack without custom code

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 Slack and GitHub. See the Tools Required section above for links to create accounts with these services.
3. Open the RepoConfig node. Add or remove items in the array to match the org and repo names you want to track, one object per repo.
4. Open the Daily Trigger node. Set the time and timezone that match your working hours.
5. Connect Slack: double click the Send Message node, choose Credential to connect with, click Create new credential, then follow the on screen steps to authorize your Slack workspace. Name the credential clearly, for example Slack Main Workspace.
6. Pick your Slack channel in the Send Message node. Ensure the Slack app or bot is invited to that channel and has permission to post.
7. Optional GitHub authentication for higher rate limits: in your GitHub account create a personal access token with read access to public repos. In the HTTP Request node, choose Credential to connect with, click Create new credential, select the GitHub or HTTP credential type as prompted, and paste the token.
8. Customize the Slack message text if needed. The template includes the repo name, release name, and a short slice of the release notes.
9. Run a test: click Execute workflow. Watch the execution to confirm each repo returns data and the If node only passes new releases.
10. Check Slack. If no message appears, confirm the channel selection, Slack credential, and that the repo actually has a new release. If the HTTP call fails, verify org and repo names and check GitHub rate limits.
11. Save and activate the workflow. Monitor the first scheduled run and adjust the schedule or repo list as your needs change.