The flow
Starts it 2Logic 6Service 5
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Notify SlackSlackService
- 3Webhook TriggerWebhookStarts it
- 4Repos to Monitor1SetLogic
- 5Repos to MonitorSetLogic
- 6FieldsSetLogic
- 7Split Out1Split OutLogic
- 8Split OutSplit OutLogic
- 9TelegramTelegramService
- 10Hook URLSetLogic
- 11Register Github WebhookHttp RequestService
- 12Get Existing HookHttp RequestService
- 13Delete Github WebhookHttp RequestService
How it's built
- Starts on
- Another system calling it
- Steps
- 13
- Size
- Medium: a working afternoon
- Connects to
- Slack, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack and Telegram accounts. 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. 13 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 13 steps before you point it at anything that matters.