Monitor multiple Github repos via webhook
What this workflow does This workflow allows you to monitor multiple Github repos simultaneously without polling due to use of Webhooks. It programmatically ...
🔌 Nodes & Integrations Used (3)
📖 Implementation & Setup Guide
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 - Can monitor multiple repos simultaneously. - Programmatically register or unregister repos from a list. No need for manual work. - Webhook notification means no constant polling necessary.
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 <YOUR GITHUB TOKEN HERE>'*. (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.
*Setup time: roughly 10 minutes.*
Instructions Video: https://vimeo.com/1013473758
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, re-enable `Webhook Trigger` and activate the workflow. - Make a commit to any of the registered repos. - Confirm that the notification went through. *That's it!*
⚡ How to import this workflow into n8n:
- Click the Direct Download JSON button above to save
Monitor multiple Github repos via webhook.json. - Log in to your n8n Cloud or self-hosted n8n instance.
- In your workflow canvas, click the menu in top-right and select Import from File (or paste the JSON directly).
- Configure your credentials (e.g. API keys, database URLs) in the corresponding node settings.
- Click Execute Workflow to test and switch to Active!
Related DevOps & GitHub Workflows
View All in DevOps & GitHub →Generate Google Doc Proposal
Production-ready n8n automation template for Generate Google Doc Proposal built by AhiXLight. Seamlessly connects Execute Workflow Trigger, Google Drive, OpenAI with 7 configured nodes.
Add a new lead to Pipedrive once GitHub repo is forked
This workflow automatically adds a new lead to Pipedrive once someone forks your GitHub repository. Prerequisites - Pipedrive account and Pipedrive credentia...
Add the affiliate to a program automatically
This workflow allows you to create an affiliate, add metadata, and add the affiliate to a program. !workflow-screenshot Tapfiliate node: This node allows you...
Add a note to Pipedrive s contact once PR is added on GitHub
This workflow automatically adds a note of the PR from GitHub to the Pipedrive contact if their GitHub email matches a Person in Pipedrive. Prerequisites - P...