Automatic email notifications for n8n version releases with Gmail
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 15 nodes and runs on a schedule (every hour). Along the way it connects Gmail.
How it runs
Trigger: On a schedule (every hour).
- n8n URL & Version References (Edit Fields (Set)): sets 3 fields: my_n8n_url, n8n_tag_1, n8n_tag_2
- Get Instance Version (HTTP Request): calls an HTTP API
- Get Latest n8n Release (HTTP Request): calls an HTTP API
- Get Beta n8n Release (HTTP Request): calls an HTTP API
- Combine Versions (Merge): merges the data from its input branches
- Version Variables (Edit Fields (Set)): sets 3 fields: my_n8n_version, n8n_tag1_version, n8n_tag2_version
- Deduplicate Beta Releases (Remove Duplicates): removes duplicate items
- Deduplicate Latest Releases (Remove Duplicates): removes duplicate items
- Set Beta Tag Info (Edit Fields (Set)): sets 3 fields: my_n8n_version, n8n_tag, n8n_version
- Set Latest Tag Info (Edit Fields (Set)): sets 3 fields: my_n8n_version, n8n_tag, n8n_version
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Markdown
n8n-nodes-base.markdown - Remove Duplicates
n8n-nodes-base.removeDuplicates - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest - Gmail
n8n-nodes-base.gmail - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
📢 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…