Monitor multiple Github repos via webhook
Ready for 3.0What this workflow does
This workflow has 13 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Slack and Telegram.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Repos to Monitor (Edit Fields (Set)): sets or maps fields
- Fields (Edit Fields (Set)): sets 7 fields: repo, repo_avatar, date…
- Split Out: splits a list into separate items
- Telegram: uses Telegram
- Register Github Webhook (HTTP Request): calls an HTTP API (POST)
- Repos to Monitor (Edit Fields (Set)): sets or maps fields
- Split Out: splits a list into separate items
- Hook URL (Edit Fields (Set)): sets 1 field: url
- Get Existing Hook (HTTP Request): calls an HTTP API
- Delete Github Webhook (HTTP Request): calls an HTTP API (DELETE)
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Split Out
n8n-nodes-base.splitOut - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack - Telegram
n8n-nodes-base.telegram - Webhook
n8n-nodes-base.webhook
From the author
What this workflow does This workflow allows you to monitor multiple Github repos simultaneously without polling due to use of Webhooks. It programmatically allows for adding and deleting of repos to your watchlist to make management convenient. Description -…