- Home
- Integrations
- n8n
Integration · Developers
Uptimecheck in n8n
Start an n8n workflow when a monitor goes down or recovers, and create monitors, acknowledge incidents, start maintenance or post status updates from any workflow.
14-day free trial · Then free on 20 monitors · No credit card
What you get
-
A trigger on every alert
The Uptimecheck Trigger starts a workflow on the events you pick: outages and recoveries, slow responses, expiring certificates and domains, DNS changes, server restarts, and site and email issues.
-
Sets itself up
Activating the workflow creates a webhook alert channel in your workspace, on every monitor, only on new ones or on none. Turning the workflow off deletes it.
-
Signed deliveries
The trigger checks each delivery’s HMAC-SHA256 signature with the channel’s own secret and refuses deliveries older than 5 minutes.
-
Act from a workflow
The Uptimecheck node creates, pauses, resumes and deletes monitors, acknowledges incidents, starts maintenance windows, posts status updates and reads the workspace summary.
How to connect n8n
-
Create an API key under Settings › API. Pick Read & write if the workflow uses the trigger or changes anything.
-
In n8n, open Settings › Community nodes, choose Install and enter
n8n-nodes-uptimecheck. -
Add an Uptimecheck or Uptimecheck Trigger node and create an Uptimecheck API credential with your key.
-
For the trigger, pick the Events and the Monitors it covers, then activate the workflow.
Your n8n must be reachable at a public address for the trigger, since Uptimecheck doesn’t send alerts to private networks. The API behind each operation is in the API reference.
On Professional and Business, with an API key from Settings › API. The trigger and every change need a read & write key.
What it can do
- Monitor: Get Many
- Monitor: Get
- Monitor: Create
- Monitor: Pause
- Monitor: Resume
- Monitor: Delete
- Incident: Get Many
- Incident: Get
- Incident: Acknowledge
- Maintenance Window: Start
- Status Update: Post
- Summary: Get
- Uptimecheck Trigger
Operations in blue change something and need a read & write key. So does the trigger, which creates its own webhook alert channel.
- Uptimecheck Trigger · monitor.down
- Uptimecheck · Status Update: Post
Uptimecheck Trigger output
{
"event": "monitor.down",
"workspace": "Northwind",
"monitor": {
"id": "mon_9xk2m1q8w4",
"name": "Checkout",
"target": "https://northwind.shop/checkout",
"url": "https://app.uptimecheck.com/w/northwind/monitors/mon_9xk2m1q8w4"
},
"incident": {
"id": "inc_7b3t9r2m5c",
"url": "https://app.uptimecheck.com/w/northwind/incidents/inc_7b3t9r2m5c"
},
"cause": "HTTP 502",
"regions": ["eu-north"],
"at": "2026-10-16T03:12:04.000Z",
"downtimeSeconds": null,
"explanation": null
}
Questions
How do I install the Uptimecheck node?
In n8n, open Settings › Community nodes, choose Install and enter n8n-nodes-uptimecheck. Then create an Uptimecheck API credential with an API key from Settings › API in Uptimecheck.
Which events can start a workflow?
Monitor down and up, slow and fast again, certificate and domain expiring, DNS changed, server rebooted, site issues, page speed dropped, email setup issues and test. Monitor down and up are picked by default.
How does the trigger know a request came from Uptimecheck?
Each delivery is signed: x-uptimecheck-signature is an HMAC-SHA256 of the timestamp and the body, keyed with the secret of the webhook channel the trigger created. A wrong signature gets 401, and deliveries older than 5 minutes are refused.
What happens when I turn the workflow off?
The trigger deletes the webhook alert channel it created, which takes it off every monitor too. Activating the workflow again creates a new one.
Which plans include it?
Professional and Business, like the REST API. Reading works with a read-only key; creating, pausing, acknowledging and the trigger need a read & write key.
Works well with
All integrations-
Webhooks
Every alert as signed JSON to your own endpoint, with retries. How it works : Webhooks -
Terraform
Monitors, projects, alert channels and status pages as code, from the Terraform Registry. How it works : Terraform -
MCP server
Let Claude, Cursor or VS Code check status and manage monitors with an API key. How it works : MCP server
Hear it from us, not your customers.
Click around the live demo without an account, or start your trial and add your first monitor.
14-day free trial · Then free on 20 monitors · No credit card