Automation library · Alerts and monitoring

WordPress Content Decay Detector with Refresh Alerts

Started by a clock, and works across Telegram. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 6Service 3

The steps in the order they run, from what starts it.

  1. 1Every Wednesday 8 AMSchedule triggerStarts it
  2. 2Site ConfigurationCodeLogic
  3. 3Fetch Posts (Oldest Modified First)Http RequestService
  4. 4Detect Content DecayCodeLogic
  5. 5Decay Detected?IfLogic
  6. 6Format Decay ReportCodeLogic
  7. 7All Content FreshNo OpLogic
  8. 8Send Decay Alert via TelegramTelegramService
  9. 9Send Decay Alert via SlackHttp RequestService
  10. 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 it

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 10 steps before you point it at anything that matters.