AltFTool original, tested in n8nEngineeringDevOps

Website uptime monitor with status alerts - n8n workflow template

A lightweight uptime checker you can run on your own n8n instance. Every five minutes it requests each URL on your list and decides whether the site is healthy. The HTTP Request node is set to return the full response and never fail on an error status, and the node itself…

Written and tested by AltFTool

Starts on
On a schedule
Nodes
8 nodes
Level
Beginner
Setup
About 3 min

Workflow preview

How this workflow runs

  1. 1

    Run manually

    Starts the workflow manually when you click 'Execute workflow' — used for testing and manual runs.

  2. 2

    Every 5 minutes

    Starts the workflow automatically on a schedule (cron / fixed interval).

  3. 3

    Sites to check

    Runs custom JavaScript to transform or manipulate the data flowing through the workflow.

  4. 4

    Check site

    Makes an external API call (HTTP request) to send or retrieve data from a third-party service.

  5. 5

    Evaluate result

    Runs custom JavaScript to transform or manipulate the data flowing through the workflow.

  6. 6

    Site is down?

    Branches the workflow based on a true/false condition.

  7. 7

    Write alert message

    Sets or transforms workflow data — prepares, renames, or injects fields before the next step.

  8. 8

    Site is up

    A pass-through step that does nothing — used to organize the flow.

Overview and setup

How it works

A lightweight uptime checker you can run on your own n8n instance. Every five minutes it requests each URL on your list and decides whether the site is healthy.

The HTTP Request node is set to return the full response and never fail on an error status, and the node itself continues on error. That means timeouts, DNS failures and refused connections arrive as data instead of stopping the run. A Code node then marks each site as up (status below 400) or down, and records the status code, the error text and the time of the check.

Down sites go through an IF node to Write alert message, which builds a ready-to-send line such as "Site down: Shop (https://shop.example.com) - HTTP 503". Healthy sites end on a No Op node.

Set up steps

  1. Import the workflow and open Sites to check.
  2. Replace the sample entries with your own names and URLs.
  3. Click Execute workflow to see one result per site.
  4. Connect a notification node of your choice after Write alert message and map message.
  5. Activate the workflow.

Customise it

  • Change the 10-second timeout in Check site to suit slow pages.
  • Check for a keyword in the page body by reading $json.body in Evaluate result.
  • Change the schedule interval, or add a Remove Duplicates node so you are only alerted once per outage.
  • Write every result to a sheet or database to build an uptime history.

n8n nodes used (7 types)

What every node does (8)
  • Run manually (Manual Trigger)Starts the workflow manually when you click 'Execute workflow' — used for testing and manual runs.
  • Every 5 minutes (Schedule Trigger)Starts the workflow automatically on a schedule (cron / fixed interval).
  • Sites to check (Code)Runs custom JavaScript to transform or manipulate the data flowing through the workflow.
  • Check site (HTTP Request)Makes an external API call (HTTP request) to send or retrieve data from a third-party service.
  • Evaluate result (Code)Runs custom JavaScript to transform or manipulate the data flowing through the workflow.
  • Site is down? (If)Branches the workflow based on a true/false condition.
  • Write alert message (Set)Sets or transforms workflow data — prepares, renames, or injects fields before the next step.
  • Site is up (No Op)A pass-through step that does nothing — used to organize the flow.

FAQ

Website uptime monitor with status alerts: questions

How do I import the "Website uptime monitor with status alerts" workflow into n8n?

Copy the workflow JSON from this page, open the n8n editor, click on an empty canvas and paste with Ctrl+V (Cmd+V on macOS). You can also download the .json file and choose Import from File in the workflow menu. Save the workflow, then attach credentials before activating it.

Which nodes and credentials does "Website uptime monitor with status alerts" use?

It uses Manual Trigger, Schedule Trigger, Code, HTTP Request, If and Set, plus 1 more. Any node that connects to an external service needs your own credential — open each node after import and select or create one. Trigger, logic and transformation nodes usually need no credentials.

Can it run on n8n Cloud and on self-hosted n8n?

The workflow format is the same on both. If a node appears as unknown or outdated after import, update n8n to a recent version or, on self-hosted instances, install the required community node package. Features such as $env access are available on self-hosted instances only.

How can I customise "Website uptime monitor with status alerts"?

Start by changing the trigger (schedule, webhook or app event) and the destination nodes to match your stack — it is listed under Engineering, DevOps. Edit prompts, field mappings and filters in the relevant nodes, use expressions like {{ $json.field }} to map data, and test with a manual execution before activating.

Related n8n workflows

Discover more

More from AltFTool

n8n is a trademark of n8n GmbH. AltFTool is not affiliated with, endorsed by or sponsored by n8n. Community templates are credited to their creators and link to the original listing; AltFTool originals are written and tested by the AltFTool team.