The flow
Starts it 1Logic 6Service 3
The steps in the order they run, from what starts it.
- 1Every Wednesday 8 AMSchedule triggerStarts it
- 2Site ConfigurationCodeLogic
- 3Fetch Posts (Oldest Modified First)Http RequestService
- 4Detect Content DecayCodeLogic
- 5Decay Detected?IfLogic
- 6Format Decay ReportCodeLogic
- 7All Content FreshNo OpLogic
- 8Send Decay Alert via TelegramTelegramService
- 9Send Decay Alert via SlackHttp RequestService
- 10Log Decay MetricsCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 10, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Telegram 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. 10 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 10 steps before you point it at anything that matters.