The flow
Starts it 1Logic 9Service 8
The steps in the order they run, from what starts it.
- 1Daily Schedule 7 AMSchedule triggerStarts it
- 2ConfigurationSetLogic
- 3Fetch RDAP BootstrapHttp RequestService
- 4Build TLD MapCodeLogic
- 5Read Sites From SheetGoogle SheetsService
- 6Loop Over SitesSplit In BatchesLogic
- 7Aggregate ResultsCodeLogic
- 8Prepare DomainCodeLogic
- 9Is Digest Day?IfLogic
- 10Check Domain (RDAP)Http RequestService
- 11Send Weekly SummaryTelegramService
- 12End - Not Digest DayNo OpLogic
- 13Check SSLHttp RequestService
- 14Check UptimeHttp RequestService
- 15Analyze & Compute TierCodeLogic
- 16Alert Needed?IfLogic
- 17Send Telegram AlertTelegramService
- 18Log to HistoryGoogle SheetsService
How it's built
- Starts on
- A clock
- Steps
- 18, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Sheets, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Sheets and Telegram accounts. 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. 18 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.
Nothing 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 18 steps before you point it at anything that matters.