Keep your team updated on new GitHub releases without manual checks. This setup watches selected repositories on a schedule and posts clear, translated release notes to Slack.

A timed trigger runs every 10 minutes during work hours. A code node holds the list of repositories you care about. For each repo, the RSS reader pulls the latest release item. Errors route to a dedicated Slack channel. Redis stores the last processed release so you never post the same update twice. New items go through Gemini to extract features, fixes, and other notes, then translate the summary into Chinese. Dates are formatted for clarity, and a code node builds clean Slack message blocks before sending.

Set up Slack, Google Gemini, and Redis credentials in n8n. Public GitHub feeds do not need login. Expect to cut daily release monitoring from manual checks to a quick glance in Slack, with consistent updates for product, QA, and support. Add your repositories, set your Slack channel, adjust the schedule, and you are ready to go.

• Scheduled checks with a cron rule that runs every 10 minutes during work hours.
• Repository list managed in a code node using simple owner and repo entries.
• RSS reader pulls the latest GitHub release items for each repository.
• Redis get and set nodes track the last processed release to prevent repeats.
• If checks handle new item detection and route errors to Slack.
• Limit node controls message volume to avoid channel noise.
• Gemini model extracts features and fixes and translates content based on a system prompt.
• DateTime node formats the release date for clear reading.
• Slack node sends rich block messages to a chosen channel with custom sender name.

• Reduce manual release checks from 30 minutes a day to 2 minutes.
• Avoid duplicate posts by tracking the last release in Redis.
• Share translated release notes in Chinese for wider team access.
• Support many repositories without extra work using scheduled loops.
• Keep messages consistent with a reusable Slack block template.
• Catch issues fast with error alerts in a separate Slack channel.

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, Google Gemini, Redis and GitHub. See the Tools Required section above for links to create accounts with these services.
3. Open the Cron Trigger node and adjust the schedule if needed. The default rule checks every 10 minutes between 9 AM and 11 PM.
4. Double click the Slack Send Message node. In the 'Credential to connect with' dropdown, click 'Create new credential' and follow the on screen instructions. In your Slack app, add chat:write and chat:write.customize scopes, install the app, then paste the Bot User OAuth token into n8n.
5. Double click the Slack Send Error node and select the same Slack credential. Set the error channel ID where alerts should go.
6. Double click the Gemini node. In the 'Credential to connect with' dropdown, click 'Create new credential' and follow the on screen instructions. Create an API key in your Google AI account and paste it into n8n.
7. Open the Redis Get and Redis Set nodes. In the credential dropdown, click 'Create new credential' and enter your Redis host, port, and password. Test the connection.
8. Open the GitHub Config code node and edit the array. Add each repository as owner/repo. No GitHub credential is required for public release feeds.
9. Open the Information Extractor node. Review the system prompt and change the target language or summary style if needed.
10. Open the DateTime node and confirm the timezone option and the custom format yyyy-MM-dd HH:mm match your needs.
11. Open the Code for Slack Tpl node and adjust the block layout if you want different fields in Slack.
12. Set the channel ID in the Slack Send Message node. Save the workflow, then click Execute once to test. Check Slack for a message and confirm Redis keys were created.
13. If no message appears, ensure the repository has a recent release in its RSS feed, confirm Slack scopes and token, verify Redis connectivity, and lower the Limit node if items are being capped.