Skip to main content

Automated website uptime monitor with email alerts & GitHub status page update

Workflow preview

Workflow preview
100%
Automated website uptime monitor with email alerts & GitHub status page update preview
Open on n8n.io

Important notice

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

1. Workflow Overview

️ Automated Website Uptime Monitor with Email Alerts & GitHub Status Page Update This n8n workflow continuously monitors your website’s availability, sends email alerts when the server goes down,...

Best for

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

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.github, n8n-nodes-base.gmail, n8n-nodes-base.switch, n8n-nodes-base.extractfromfile, n8n-nodes-base.code

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automated website uptime monitor with email alerts & GitHub status page update
Workflow name
Automated website uptime monitor with email alerts & GitHub status page update

🖥️ Automated Website Uptime Monitor with Email Alerts & GitHub Status Page Update

This n8n workflow continuously monitors your website’s availability, sends email alerts when the server goes down, and automatically updates a status page (index.html) in your GitHub repository to reflect the live status.


📌 Good to Know

  • The workflow checks your website every 2 minutes (interval configurable).
  • If the website is down (503, bad response, or error) → it sends an email alert and updates the GitHub-hosted status page to show Down.
  • If the website is up (200) → it updates the GitHub-hosted status page to show Up.
  • The email notification includes an HTML-formatted alert page.
  • You can use GitHub Pages to host the status page publicly.

ℹ️ What is GitHub Pages?

  • GitHub Pages is a free hosting service provided by GitHub that lets you publish static websites (HTML, CSS, JS) directly from a GitHub repository.
  • You can use it to make your index.html status page publicly accessible with a URL like:

⚡ How to Set Up GitHub Pages for Your Status Page

  1. Create a new repository on GitHub (recommended name: status).
  2. Add a blank index.html file (n8n workflow will later update this file).
  3. Go to your repository → SettingsPages.
  4. Under Source, select the branch (main or master) and folder (/root).
  5. Save changes.
  6. Your status page will now be live at: https://<USERNAME>.github.io/status

✅ Prerequisites

  • An n8n instance (self-hosted or cloud).
  • A GitHub account & repository (to host the status page).
  • A Gmail account (or any email service supported by n8n – example uses Gmail).
  • Access to the target website URL you want to monitor.

⚙️ How it Works

  1. Schedule Trigger → Runs every 2 minutes.
  2. HTTP Request → Pings your website URL.
  3. Switch Node → Evaluates the response status (200 OK vs error/503).
  4. Code Node → Generates a dynamic HTML status page (Up/Down).
  5. GitHub Repo & File → Github Repo Name Should be https://github.com/<OWNER_NAME>/status (recommended) & Must have(required) a blank file named as index.html before triggering this flow.
  6. GitHub Node → Updates/commits the index.html file in your repository.
  7. Gmail Node → Sends an email alert if the site is down.

🚀 How to Use

  1. Import the workflow JSON into your n8n instance.
  2. Configure credentials for:
    • GitHub (Personal Access Token with repo permissions).
    • Gmail (or your preferred email service).
  3. Replace the following:
    • https://app.yourdomain.com/health → with your own website URL.
    • [email protected] → with your email address (or distribution list).
    • GitHub repo details → with your repository where index.html will live.
  4. Deploy the workflow.
  5. (Optional) Enable GitHub Pages on your repo to serve index.html as a live status page.

🛠 Requirements

  • n8n v1.0+
  • GitHub personal access token
  • Gmail API credentials (or SMTP/email service of your choice)

🎨 Customising this Workflow

  • Interval → Change schedule from 2 minutes to any desired frequency.
  • Email Content → Modify HTML alert template in the Gmail node.
  • Status Page Styling → Edit the HTML/CSS in the Code node to match your branding.
  • Error Handling → Extend Switch node for other status codes (e.g., 404, 500).
  • Multiple Websites → Duplicate HTTP Request + Switch nodes for multiple URLs.

👤 Who Can Use It?

  • DevOps & SRE Engineers → For automated uptime monitoring.
  • Freelancers/Developers → To monitor client websites.
  • Startups & SMEs → For a free, lightweight status page without paid tools.
  • Educators/Students → As a hands-on learning project with n8n.

🌟 Key Features

  • 🔄 Automated uptime checks (configurable interval).
  • 📧 Email notifications on downtime.
  • 📝 Dynamic HTML status page generation.
  • 🌍 GitHub Pages integration for public visibility.
  • ⚡ Lightweight & cost-effective (no paid monitoring tool needed).

🔗 Tools Integration

  • n8n – Orchestration & automation.
  • GitHub – Version control + hosting of status page.
  • Gmail – Email notifications.
  • HTTP Request – Website availability check.

📈 Example Use Cases

  • Personal website monitoring with public status page.
  • Monitoring SaaS apps & notifying support teams.
  • Internal company services uptime dashboard.

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 - Schedule Trigger

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

Block 2 - HTTP Request

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

Block 3 - Sticky Note

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

Block 4 - Sticky Note1

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

Block 5 - Sticky Note4

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

Block 6 - Sticky Note2

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

Block 7 - Sticky Note5

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

Block 8 - Sticky Note6

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

Block 9 - Sticky Note7

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

Block 10 - Sticky Note8

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

Block 11 - Update Index.html file

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

Block 12 - Send a notification mail

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 13 - Switch - status code

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

Block 14 - Extract from File - Generated HTML

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

Block 15 - Template HTML Code

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

Block 16 - Get existing index.html file

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

Block 17 - Extract from existing File (github)

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

Block 18 - If - Compare existing HTML file with generated HTML

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

Block 19 - Sticky Note3

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

3. Summary Table

Workflow Automated website uptime monitor with email alerts & GitHub status page update
Complexity advanced
Nodes 19
Categories DevOps
Author Linearloop Team
Published 16 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8624/8624.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 Automated website uptime monitor with email alerts & GitHub status page update do?

️ Automated Website Uptime Monitor with Email Alerts & GitHub Status Page Update This n8n workflow continuously monitors your website’s availability, sends email alerts when the server goes down,...

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.