How to use Uptimecheck in n8n

Updated November 15, 2026 2 min read

On Professional and Business, the Uptimecheck community node for n8n, n8n-nodes-uptimecheck, adds two nodes. Uptimecheck Trigger starts a workflow when Uptimecheck sends an alert, and Uptimecheck works with monitors, incidents, maintenance windows and status updates from any workflow.

Install the node

  1. In n8n, open Settings › Community nodes.
  2. Choose Install, enter n8n-nodes-uptimecheck and confirm.

Add your API key

  1. In Uptimecheck, open Settings › API and choose New API key. Pick Read only if your workflows only read, or Read & write for the trigger and for anything that creates, pauses or acknowledges.
  2. Choose Create key and copy it. This is the only time the key is shown.
  3. In n8n, add an Uptimecheck node, create a new Uptimecheck API credential and paste the key into API Key. Leave Base URL as it is.

Start a workflow on alerts

  1. Add an Uptimecheck Trigger node with your credential.
  2. Under Events, pick what starts the workflow. Monitor Down and Monitor Up are picked by default; slow and fast again, certificate and domain expiring, DNS changed, server rebooted, site issues, page speed dropped, email setup issues and test can be added.
  3. Under Monitors, choose All Monitors to cover every monitor you have now and new ones, New Monitors Only for monitors created from now on without their own alert channels, or None to pick them yourself in Uptimecheck.
  4. Activate the workflow. A webhook alert channel named “n8n:” and the workflow’s name appears under Alert channels in Uptimecheck.

Each delivery is signed. The trigger checks x-uptimecheck-signature, an HMAC-SHA256 of the timestamp and the body keyed with the channel’s own secret, answers 401 to a wrong signature and refuses deliveries older than 5 minutes. Events you didn’t pick are ignored. Turning the workflow off deletes the alert channel again.

Your n8n must be reachable at a public address, because Uptimecheck doesn’t send alerts to private networks. To try it, pick the Test event and choose Send test on the new alert channel. The workflow gets the alert as Uptimecheck sends it: event, workspace, monitor, incident for outages and recoveries, cause, regions, at and downtimeSeconds. Every field is described under webhook alerts.

What the Uptimecheck node can do

  • Monitor: Get Many, Get, Create (website or API, port, ping, domain expiry or cron job), Pause, Resume and Delete.
  • Incident: Get Many (only open ones, or all), Get and Acknowledge.
  • Maintenance Window: Start one now for the monitor IDs you give, for the number of minutes you set (30 by default).
  • Status Update: Post one on a status page with the status Investigating, Identified, Monitoring, Resolved or Notice, and optionally notify its subscribers.
  • Summary: Get the number of monitors per status and the open incidents.

IDs such as mon_…, inc_… and sp_… come from Get Many or from the trigger’s output. A list comes back as one item per monitor or incident.

Example: a status update when a monitor goes down

  1. An Uptimecheck Trigger with the event Monitor Down.
  2. An Uptimecheck node with Status Update › Post: your Status Page ID, a Title such as {{ $json.monitor.name }} is down, the status Investigating and a Message. Turn on Notify Subscribers to tell them too.

More on the n8n integration, API keys and the REST API.

Integrations n8n Webhooks

Was this article helpful?

Try it in your own workspace

14-day free trial · Then free on 20 monitors · No credit card

Still stuck?

Email support@uptimecheck.com and we will reply within 24 hours.

Automating it? The API reference covers the REST API, webhooks, cron job pings and MCP.