The flow
Starts it 3Logic 4Service 3
The steps in the order they run, from what starts it.
- 1Heartbeat PingWebhookStarts it
- 2Every 15 MinutesSchedule triggerStarts it
- 3Every Morning 9:00Schedule triggerStarts it
- 4Record PingCodeLogic
- 5Check Job DeadlinesCodeLogic
- 6Build Daily Status ReportCodeLogic
- 7Failure Reported?IfLogic
- 8Alert: Missed HeartbeatTelegramService
- 9Send Daily SummaryTelegramService
- 10Alert: Job Reported FailureTelegramService
How it's built
- Starts on
- Another system calling it
- 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 another system calling it.
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.