Automation library · Alerts and monitoring

Notify on server restarts with Discord and Telegram

Started by an event in a connected app, and works across Discord, Slack and Telegram. 11 steps: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
3Services it connects to

The flow

Starts it 1Logic 5Service 5

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

  1. 1When Server RestartedN8n triggerStarts it
  2. 2Set Execution ParametersSetLogic
  3. 3Fetch Execution LogsN8nService
  4. 4Merge Execution DataMergeLogic
  5. 5Filter Recent ExecutionsFilterLogic
  6. 6Process Data in JavaScriptCodeLogic
  7. 7Summarize Execution DataSummarizeService
  8. 8Ping Discord ChannelDiscordService
  9. 9Send Telegram MessageTelegramService
  10. 10Post to Slack ChannelSlackService
  11. 11Sort Execution SummarySortLogic

How it's built

Starts on
An event in a connected app
Steps
11
Size
Medium: a working afternoon
Connects to
Discord, Slack, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Discord, Slack and Telegram accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

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