Stay on top of code reviews and issues without watching your inbox. This setup checks for new GitHub notifications and posts a clean summary into a Discord channel so your team can act fast. It is ideal for engineering teams who want quick alerts without extra tools.

A schedule runs every minute. A small script calculates the time one minute ago and passes it to the GitHub notifications API. The request uses Basic Auth and a User Agent, and only asks for updates since the last minute to cut noise. Another script turns each notification into a short line with reason, title, and a readable link. A check step only sends to Discord when there is something new, then the message tags a user so the right person sees it.

You need a GitHub account with a personal access token and a Discord webhook or bot access. Set your channel, add the user ID you want to mention, and decide how often it should run. Teams use this for code review nudges, bug triage, and release follow ups. Expect faster replies and less context switching across busy repos.

• Scheduled check runs every minute using a cron trigger.
• Dynamic time window calculates one minute ago for precise polling.
• GitHub notifications API call with Basic Auth and custom User Agent.
• Message builder formats reason, title, and a clean web link for each item.
• Conditional step prevents empty posts when no updates are found.
• Discord message posts to a channel and mentions a specific user ID.

• Reduce manual GitHub inbox checks to a few minutes per day
• Send alerts only when new items arrive to cut channel noise
• Speed up code review turnaround by getting instant pings
• Connect GitHub and Discord so teams act in one place
• Handle many repos without extra effort by using one feed

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 Discord. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager or by opening the HTTP Request node, create a new credential for GitHub using Basic Auth. Use your GitHub username and a personal access token as the password.
4. Create a GitHub personal access token in your GitHub settings. Give it the scopes needed to read notifications and repos. Copy the token and store it securely.
5. Open the Cron node and confirm it is set to run every 1 minute. Adjust the interval if your team needs a different cadence.
6. Open the @Get Date 1 min ago function node and leave it as is for a one minute window. For testing, you can temporarily change it to more minutes to pull sample data.
7. Open the @Get Issue HTTP Request node and verify the URL points to the GitHub notifications endpoint and that the query parameter since uses the output of the date node.
8. Open the Discord node. Double click the node, then on the Credential to connect with dropdown click Create new credential and follow the on screen instructions to connect your Discord webhook or bot. Set the target channel.
9. Replace the placeholder mention in the Discord text with a real user ID like <@1234567890>. In Discord, enable Developer Mode and copy the user ID from the profile menu.
10. Run the workflow once manually to test. Make sure you have at least one unread notification in GitHub within the chosen window. Check the execution log and confirm a message posts in the selected Discord channel.
11. If you see no messages, review the IF node path. If GitHub returns 401 or 403, recreate the credential with the correct token. If Discord fails, verify the webhook or bot permissions for that channel.