Automation library · Alerts and monitoring

Twitch stream TG/Line notify with Telegram

Started by another system calling it, and works across Telegram. 10 steps, 3 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 3Service 5

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

  1. 1Twitch event webhookWebhookStarts it
  2. 2Switch ChannelSwitchLogic
  3. 3If Challenge eventIfLogic
  4. 4Respond chanllenge requestRespond To WebhookStarts it
  5. 5Get Channel InfoHttp RequestService
  6. 6If Stream Online1IfLogic
  7. 7TG online messageTelegramService
  8. 8TG offline messageTelegramService
  9. 9Line : Push Online MessageHttp RequestService
  10. 10Line : Push Offline MessageHttp RequestService

How it's built

Starts on
Another system calling it
Steps
10, with 3 branches
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 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.