The flow
Starts it 1Logic 11Service 4
The steps in the order they run, from what starts it.
- 1Every Monday at 9amSchedule triggerStarts it
- 2Set VariablesSetLogic
- 3Split Watched ReposSplit OutLogic
- 4Fetch GitHub Trending PageHttp RequestService
- 5Split Tracked EntitiesSplit OutLogic
- 6Fetch Latest ReleaseHttp RequestService
- 7Parse Trending HTMLCodeLogic
- 8Fetch Entity DataHttp RequestService
- 9Aggregate ReleasesCodeLogic
- 10Merge All DataMergeLogic
- 11Extract CommitsCodeLogic
- 12Merge Releases + CommitsMergeLogic
- 13Has Any Content?IfLogic
- 14Build Combined EmailCodeLogic
- 15Do NothingNo OpLogic
- 16Send Weekly DigestGmailService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Gmail
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.