Send weekly GitHub digest with releases, commits and trending repos via 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 16 nodes and runs on a schedule (every week at 09:00). Along the way it connects Gmail. It also calls github.com over HTTP.
How it runs
Trigger: On a schedule (every week at 09:00).
- Set Variables (Edit Fields (Set)): sets 4 fields: recipient_email, days_back, release_repos…
- Split Watched Repos (Split Out): splits a list into separate items
- Fetch GitHub Trending Page (HTTP Request): calls github.com
- Split Tracked Entities (Split Out): splits a list into separate items
- Fetch Latest Release (HTTP Request): calls an HTTP API
- Parse Trending HTML (Code): runs custom JavaScript code
- Fetch Entity Data (HTTP Request): calls an HTTP API
- Aggregate Releases (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Extract Commits (Code): runs custom JavaScript code
…plus 4 more steps. See the full node list below.
Services it uses
HTTP calls to: github.com
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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Split Out
n8n-nodes-base.splitOut - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - No Operation, do nothing
n8n-nodes-base.noOp - Edit Fields (Set)
n8n-nodes-base.set
From the author
Send Weekly GitHub Digest with Releases, Commits, and Trending Repos Stay on top of the GitHub ecosystem with a single automated weekly email covering it all. How it works 1. A schedule trigger fires every Monday at 9am and reads your config variables. Feel…