Skip to main content

GitHub fork status monitor

Workflow preview

Workflow preview
100%
GitHub fork status monitor preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow helps you keep an eye on your GitHub forks, notifying you when they fall behind or pull ahead of their upstream repositories. How It Works Fetches All Your Repos: The workflow starts ...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.github, n8n-nodes-base.telegram, n8n-nodes-base.telegramtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Manish.

Original n8n.io source

1.1 Workflow description

Title
GitHub fork status monitor
Workflow name
GitHub fork status monitor

This workflow helps you keep an eye on your GitHub forks, notifying you when they fall behind or pull ahead of their upstream repositories.

How It Works

  • Fetches All Your Repos: The workflow starts by grabbing a list of all repositories owned by your GitHub account.
  • Filters for Forks: It then intelligently filters this list to identify only your forked repositories.
  • Compares Branches: For each identified fork, it compares its default branch against the upstream repository's default branch to find out how many commits it's ahead or behind.
  • Filters for Changes: Only forks that are either ahead or behind their upstream (i.e., not perfectly in sync) are processed further.
  • Generates Report: A concise, well-formatted report is compiled, highlighting the status and commit differences for each relevant fork.
  • Sends Telegram Notification: Finally, this report is sent directly to your Telegram chat, keeping you informed in real-time.

Setup Steps

  • Copy the template
  • Update triggers ( optional )
  • Update the credentials

Prerequisites

  • GitHub Credentials: You'll need to provide your GitHub personal access token for the "Get All Repositories" and "Compare Branches API Call" nodes.
  • Telegram Bot Setup: Configure a Telegram Bot and obtain its API token and your chat ID for the "Send Report" node.
  • Github Owner Username: Update the "Get All Repositories" node with the GitHub username of the repository owner whose forks you want to monitor.

Explore & Fine-Tune: All detailed instructions and explanations, including how to adjust the filtering logic or output formatting, are provided in sticky notes directly within the workflow canvas.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 3 - get-repo-details

Type / Role
n8n-nodes-base.github - github
Config choices
Version 1.1

Block 4 - Telegram

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 5 - Telegram Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 6 - Prepare Upstream URL

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Compare Branches API Call

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 8 - Process Comparison Result

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Combine Results

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 10 - Format for Telegram

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 13 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Get repos

Type / Role
n8n-nodes-base.github - github
Config choices
Version 1.1

Block 17 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Filter forked repositories only

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.2

3. Summary Table

Workflow GitHub fork status monitor
Complexity advanced
Nodes 19
Categories DevOps
Author Manish
Published 11 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4878/4878.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does GitHub fork status monitor do?

This workflow helps you keep an eye on your GitHub forks, notifying you when they fall behind or pull ahead of their upstream repositories. How It Works Fetches All Your Repos: The workflow starts ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.