Templates / Monitor multiple Github repos via webhook

Monitor multiple Github repos via webhook

Ready for 3.0

by Jay Hartley ✓ · 6,349 views · created 2024-09-27 · DevOps

Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.

What 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).

  1. Repos to Monitor (Edit Fields (Set)): sets or maps fields
  2. Fields (Edit Fields (Set)): sets 7 fields: repo, repo_avatar, date…
  3. Split Out: splits a list into separate items
  4. Telegram: uses Telegram
  5. Register Github Webhook (HTTP Request): calls an HTTP API (POST)
  6. Repos to Monitor (Edit Fields (Set)): sets or maps fields
  7. Split Out: splits a list into separate items
  8. Hook URL (Edit Fields (Set)): sets 1 field: url
  9. Get Existing Hook (HTTP Request): calls an HTTP API
  10. Delete Github Webhook (HTTP Request): calls an HTTP API (DELETE)

…plus 1 more step. See the full node list below.

Services it uses

SlackTelegram

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)

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 -…

Excerpt from Jay Hartley's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.