Automate GitHub Release Emails with n8n HTTP and Email Nodes

What This Workflow Does

This workflow checks a GitHub repository every day for new releases.
It finds out if a release was made in the last 24 hours.
If yes, it sends an email with the release notes in formatted HTML.
If no new release is found, it does not send an email.
This saves time and helps the user not miss updates.

The workflow fetches release info, converts notes from markdown to HTML, and emails the details automatically.
It runs daily and alerts the right people without spam or manual checking.

Who Should Use This Workflow

Anyone needing updates on GitHub releases without checking manually will find this useful.
It fits project managers, developers, and teams watching public or private repos.

Users who want simple automated email alerts with nicely formatted release notes can rely on this workflow.
It avoids missed news and saves daily minutes spent on manual checks.

Tools and Services Used

• n8n Automation Platform: Runs the workflow nodes and handles automation.
• GitHub API: Provides latest release data for specified repositories.
• Email SMTP Server: Sends release notification emails using user credentials.

The service requires a GitHub repo URL and valid SMTP credentials set up in n8n.
For private repos, GitHub token is needed for API access.

Inputs, Processing Steps, and Output Explained

Inputs

• GitHub API URL to get latest release JSON.
• SMTP credentials to send emails.
• Recipient email address(es) for notifications.

Processing Steps

• Schedule Trigger runs daily to start workflow.
• HTTP Request node calls GitHub API to fetch latest release data.
• If node tests if release date is within last 24 hours.
• Split Out node extracts the release notes markdown text.
• Markdown node converts markdown text to HTML.
• Email Send node emails formatted release notes to recipients.

Output

An email arrives with formatted release details only when there is a new release in the last day.
No email is sent if releases are older than 24 hours.

Beginner Step-by-Step: How to Use This Workflow in Production

Step 1: Download the Workflow

1. Click the Download button on this page to get the workflow file.

Step 2: Import Workflow in n8n

1. Open the n8n editor interface.
2. Select Import from File option.
3. Choose the downloaded workflow file to add it inside n8n.

Step 3: Configure Credentials and Settings

1. Enter your SMTP email server credentials in the Email Send node.
2. Update the GitHub API URL in the HTTP Request node to your desired repository.
3. Set the recipient email address or list in the Email Send node.
4. If required, add GitHub API token in headers for private repositories.

Step 4: Test the Workflow

1. Run the workflow once manually to make sure it works and sends test email.

Step 5: Activate Workflow for Production

1. Turn on the workflow toggle so it runs daily as scheduled.
2. Monitor executions in the n8n logs panel.

Following these steps, you can start automatic GitHub release notifications without building the workflow from scratch.
For self-hosted or VPS users, see self-host n8n resources for stable setups.

Customizations and Tips

• Add multiple recipient emails by using comma-separated emails in the Email Send node.
• Secure private repository access by adding Authorization: Bearer YOUR_GITHUB_TOKEN header in the HTTP Request node.
• Change how often the workflow checks releases by adjusting the Schedule Trigger node interval.

These simple changes can extend the workflow for different needs and environments.
Sticky notes in the workflow can guide new users to update main parameters easily.

Common Problems and How to Fix Them

• Email sending error: Check SMTP credentials and test connection in the Email Send node.
• 404 on GitHub API call: Verify the repository URL matches https://api.github.com/repos/OWNER/REPO/releases/latest.
• No email on new release: Confirm the If node date condition is correct and matches the release date format.

Careful checks on configuration usually resolve most issues.
Review logs and expressions if unexpected behavior occurs.

Pre-Production Checklist

• Set the Schedule Trigger frequency as needed.
• Test the HTTP Request node with your repository URL.
• Check the If node returns true for recent releases.
• Confirm markdown converts to HTML correctly.
• Send test email to verify SMTP settings.
• Backup the workflow before production run.

Deployment Guide

Once testing completes, activate the workflow toggle in the n8n editor.
Ensure the n8n instance is running so scheduled triggers will work.
Use the execution log to check runs and errors.

Summary

✓ Automatic daily check for new GitHub releases.
✓ Sends email only if new release is published in last 24 hours.
✓ Converts release notes from markdown to rich HTML format.
✓ Saves manual checking time and avoids missed updates.
✓ Simple import and setup inside n8n with minimal configuration.
✓ Flexible for private repos and multiple recipients.