Skip to main content

Automatic email notifications for n8n version releases with Gmail

Workflow preview

Workflow preview
100%
Automatic email notifications for n8n version releases with Gmail preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Monitor n8n releases and get notifications for new versions This workflow automatically monitors n8n’s release channels (latest and beta) and sends you email notifications whenever a new vers...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.markdown, n8n-nodes-base.removeduplicates, n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.merge, n8n-nodes-base.httprequest, n8n-nodes-base.gmail, n8n-nodes-base.scheduletrigger

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Anan.

Original n8n.io source

1.1 Workflow description

Title
Automatic email notifications for n8n version releases with Gmail
Workflow name
Automatic email notifications for n8n version releases with Gmail

📢 Monitor n8n releases and get notifications for new versions 🆕

This workflow automatically monitors n8n’s release channels (latest and beta) and sends you email notifications whenever a new version is published. It also reads the version of your current n8n instance, allowing you to integrate automatic updates and ensure you never miss a release.

Who is this for

This workflow is designed for n8n users who want to stay informed and up to date with new releases and features without manually checking for updates, especially those managing their own instances who need to plan upgrades and review release notes.

How it works

The workflow performs the following steps:

  • Fetches version information from the npm registry (latest and beta releases)
  • Identifies only new versions by deduplication
  • Retrieves release notes from GitHub for any newly detected version
  • Converts Markdown to HTML for email template formatting
  • Sends a styled email notification including the release name, version tag, your current version, and the complete release notes

Setup

  • Configure your n8n instance URL (Set my_n8n_url) to detect your current version (optional — can be left blank)
  • Connect and authorize the Gmail account used to send emails
  • Update the recipient email address in the Gmail node

Requirements

  • A Gmail account for sending emails

Customization tips

  • Adjust the schedule trigger if hourly checks are too frequent
  • Modify the release channel (e.g., “latest” or “beta”) if you want to track a different tag
  • Change the npm registry link if you want to monitor a different package
  • Customize the email template/styling in the Gmail node
  • Add additional notification channels (Slack, Discord, etc.) alongside or instead of email
  • Extend this workflow to automatically update your n8n instance when a new release becomes available

Need help?

If you're facing any issues using this workflow, join the community discussion on the n8n forum.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Convert Notes To HTML

Type / Role
n8n-nodes-base.markdown - markdown
Config choices
Version 1

Block 2 - Deduplicate Beta Releases

Type / Role
n8n-nodes-base.removeDuplicates - removeDuplicates
Config choices
Version 2

Block 3 - Set Beta Tag Info

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 4 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Combine Versions

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 10 - Version Variables

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 11 - Deduplicate Latest Releases

Type / Role
n8n-nodes-base.removeDuplicates - removeDuplicates
Config choices
Version 2

Block 12 - Set Latest Tag Info

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Merge Releases

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 14 - Get GitHub Release Notes

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 15 - Send Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 16 - Get Latest n8n Release

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 17 - Get Beta n8n Release

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 18 - Triggers Section Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - n8n URL & Version References

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 20 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Get Instance Version

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 22 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.3

3. Summary Table

Workflow Automatic email notifications for n8n version releases with Gmail
Complexity advanced
Nodes 22
Categories DevOps
Author Anan
Published 19 Nov 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/11005/11005.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automatic email notifications for n8n version releases with Gmail do?

Monitor n8n releases and get notifications for new versions This workflow automatically monitors n8n’s release channels (latest and beta) and sends you email notifications whenever a new vers...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.