The flow
Starts it 1Logic 8Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2ConfigSetLogic
- 3Get all workflowsN8nService
- 4Get recent executionsN8nService
- 5Combine workflows and executionsMergeLogic
- 6Aggregate metricsCodeLogic
- 7Detect stalled schedulesCodeLogic
- 8Evaluate SLACodeLogic
- 9Get previous snapshotData TableService
- 10Compare to previous runCodeLogic
- 11Save snapshotData TableService
- 12Prepare report fieldsCodeLogic
- 13Compose messageSetLogic
- 14Send report to TelegramTelegramService
How it's built
- Starts on
- A clock
- Steps
- 14
- Size
- Medium: a working afternoon
- Connects to
- Telegram, n8n data table
- 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. 14 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 14 steps before you point it at anything that matters.