Bear Brown
← All N8N workflows
Messaging & emailHTTP RequestManual TriggerEdit FieldsSlackSplit Out

Monitor Multiple Github Repos

Configured with HTTP Request, Slack, Split Out, Telegram, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗13 nodes · MIT
Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerTransformSplit OutSplit OutWeb / APIRegister Github WebhookHTTP RequestTransformSplit Out1Split OutWeb / APIDelete Github WebhookHTTP RequestTransformFieldsEdit FieldsMessagingNotify SlackSlackMessagingTelegramTelegramTransformRepos to MonitorEdit FieldsTriggerWebhook TriggerWebhookTransformRepos to Monitor1Edit FieldsWeb / APIGet Existing HookHTTP RequestTransformHook URLEdit Fields

Node categories in this workflow

  • Trigger
  • Transform
  • Web / API
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Split OutTransformSplit OutSee node parameters
Register Github WebhookWeb / APIHTTP RequestPOST
Split Out1TransformSplit OutSee node parameters
Delete Github WebhookWeb / APIHTTP RequestDELETE
FieldsTransformEdit FieldsSee node parameters
Notify SlackMessagingSlackSee node parameters
TelegramMessagingTelegramSee node parameters
Repos to MonitorTransformEdit FieldsSee node parameters
Webhook TriggerTriggerWebhookSee node parameters
Repos to Monitor1TransformEdit FieldsSee node parameters
Get Existing HookWeb / APIHTTP RequestSee node parameters
Hook URLTransformEdit FieldsSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • httpHeaderAuth
  • telegramApi

Workflow notes

Monitor Multiple Github Repos

Monitor Multiple Github Repos

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.

Test

Test

1. Register Webhooks

  • In Repos to Monitor, add any repo you want to monitor changes for.
  • Disable Webhook Trigger, Click Test Workflow and if your Github credentials were set correctly, it will automatically register the webhooks. - You can test this by running the single node Get Existing Webhook and confirming it outputs the repo addresses.

2. Handle Github Events

  • Now that you have registered the webhooks, reenable Webhook Trigger and activate the workflow.
  • Make a commit to any of the registered repos.
  • Confirm that the notification went through. That's it!
Setup

Setup

1. Creating Credentials on Github

Generate a personal access token on github by following these esteps;

  • Right hand side of page -> Settings -> scroll to bottom -> Developer Settings > Personal Access Token > Tokens (classic) > Generate New Token
  • Give scopes: admin:repo_hook repo (if you want to use it for your own private repo)

if you need more help, see here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens

2. Setting Credentials in n8n

In Register Github Webhook Authenticaion > Generic Credential Type Generic Auth Type > Header Auth Header Auth > Create New Credential with Name set to 'Authorization' and Value set to 'Bearer '. (You can reuse this for Delete Github Webhook and Get Existing Webhooks). Now in Register Github Webhook, scroll down to Send Body > JSON and inside the JSON, change the value of "url" to the webhook address given as Production URL in the node Webhook Trigger.

3. Notification settings

In the third row, link up the Webhook Trigger to any API of your choice. Slack and Telegram are given as examples. You can also format the notification message as you wish.

Monitor Multiple Github Repos

Monitor Multiple Github Repos

Purpose and structure

This folder contains the Monitor Multiple Github Repos workflow. Its executable nodes use httpRequest, manualTrigger, set, slack, splitOut, telegram, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Webhook Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0585_Telegram_Splitout_Automation_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Delete All Webhooks
  • Register Webhooks
  • Handle Github Event

More in Messaging & email

Addon for Workflow Nodes Update Check TemplateAge and number of the newsAI Email Filtering Automation