Get the latest release notes from any GitHub repo sent to your inbox each day. Product and engineering teams can stay informed without opening GitHub. Quick, simple, and easy to maintain.

A daily schedule calls the GitHub releases API to pull the newest release. The flow extracts the release body, converts the markdown to clean HTML, and prepares it for email. Gmail sends the formatted notes to the address you choose. Sticky notes in the canvas show where to change the repo URL and the recipient for faster setup.

Use a Gmail OAuth credential and add a GitHub token if you want to avoid rate limits. Expect to cut manual checks and copy paste from about 20 minutes a day to under 2 minutes, with fewer mistakes. Great for teams that want a simple daily digest from a key repo, like internal tools, client projects, or open source libraries they watch.

• Daily schedule triggers the run at a time you choose
• HTTP request pulls the latest release from the GitHub API
• Split Out extracts the release body for clean processing
• Markdown to HTML converts notes into email friendly HTML
• Gmail sends the formatted message with your subject and recipient
• Sticky notes show where to update the repo URL and email

• Reduce manual checks from 20 minutes a day to under 2 minutes
• Automate 100 percent of release email delivery
• Eliminate copy and paste errors in release notes
• Connect GitHub and Gmail with no custom code
• Scale by cloning the flow to watch more repos

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 Gmail. See the Tools Required section above for links to create accounts with these services.
3. Open the Daily Trigger node and set your time zone and schedule so the email arrives at a helpful time for your team.
4. Double click the Fetch GitHub Repo Releases node. Replace the URL with your repo in this format: https://api.github.com/repos/owner/repo/releases/latest.
5. If you need higher rate limits, click Credentials in the node, choose Create new credential, and follow the steps to add a GitHub personal access token. You can add it as an Authorization header.
6. Click Execute Node on the Fetch node and confirm the output includes a body field with release notes text.
7. Open the Split Out node and confirm the field to split is set to body so only the notes are passed forward.
8. Open the Convert Markdown to HTML node and confirm it reads {{ $json.body }} and writes to the html field.
9. Double click the Send Gmail node. In the Credential to connect with dropdown, click Create new credential and sign in with the Gmail account that will send the email.
10. In Send Gmail, set the To field to your target address, adjust the Subject line, and keep the message set to {{ $json.html }}.
11. Run the workflow once manually to send a test email. Check your inbox and spam folder to confirm delivery.
12. Turn the workflow on. If emails do not arrive, check Gmail sending limits, confirm the GitHub node returns a body field, and review the Execution log for errors.