UptimeRobot n8n integrationAutomate UptimeRobot with n8n.

Returns the account details behind the API key currently selected in the node. It takes no parameters at all, which makes it the cheapest way to prove a credential works before a longer workflow depends on it.

Adds a new destination for UptimeRobot alerts to the account, and returns it so the following node can keep its identifier.

• Friendly Name: the name of the alert contact, what you will recognize it by in lists.
• Type: the contact type, picked from Boxcar (4), E-Mail (2), Pushbullet (6), Pushover (9), SMS (1), Twitter DM (3) and Webhook (5).
• Value: the matching value for that type, often {{ $json.email }} when the address comes from an earlier node.

Removes one alert contact from the account permanently. Nothing is archived, so the identifier you pass should come from a list you just read rather than from memory.

• ID: the identifier of the alert contact, typically {{ $json.id }} taken from a alertContact.getAll node placed just before.

Pulls a single alert contact back from UptimeRobot, one identifier at a time, and hands its fields to the rest of the workflow.

• ID: the identifier of the alert contact you want, hardcoded when the contact is fixed, or {{ $json.id }} when it travels with the item.

Lists the alert contacts registered on the account, one n8n item per contact.

• Return All: enabled, n8n pages through the API until every contact is returned; disabled, it stops at Limit.
• Limit: the maximum number of contacts returned when Return All stays off.
• Alert Contact IDs: in Filters, a dash-separated list of identifiers such as 236-1782-4790, to fetch a known subset in one call.

Edits a contact in place, keeping its identifier and everything you leave untouched.

• ID: the identifier of the alert contact to modify, required even when only one field changes.
• Friendly Name: in Update Fields, the new display name of the contact.
• Value: in Update Fields, the correspondent value, which can only be used if the contact is a Webhook alert contact.

Declares a maintenance window on the account and returns it, so the workflow that opened it can close it later.

• Duration (Minutes): the activation period of the window, expressed in minutes.
• Friendly Name: the name of the window, worth deriving from the release it covers.
• Type: Once (1), Daily (2), Weekly (3) or Monthly (4).
• Start Time: the start datetime of the window, often {{ $json.startsAt }} from an earlier node.
• Week Day and Month Day: optional, they pin a recurring window to a day.

Drops a maintenance window from the account. The window disappears from the configuration, so a recurring one stops coming back on its schedule.

• ID: the identifier of the maintenance window, usually carried in as {{ $json.id }} from the node that created or listed it.

Reads one maintenance window and returns its current settings, duration, type and start time included.

• ID: the identifier of the window to read, the value you stored when it was created.

Returns the maintenance windows configured on the account, one item each, ready to be filtered or counted downstream.

• Return All: on, the node pages through everything; off, it stops once Limit is reached.
• Limit: the ceiling on how many windows come back.
• Maintenance Window IDs: in Filters, identifiers separated with a dash, as in 236-1782-4790.

Changes an existing window without recreating it, which matters because the identifier stays stable for whatever references it.

• ID: the identifier of the window to edit.
• Duration (Minutes): required here too, even if you only came to change the start time.
• Friendly Name, Start Time, Type, Week Day, Month Day: in Update Fields, the five settings you can revise.

Registers a new check in UptimeRobot and returns it, identifier included, which is what makes automated onboarding possible.

• Friendly Name: the label of the monitor, the one that shows up in lists and status pages.
• Type: Heartbeat (5), HTTP(S) (1), Keyword (2), Ping (3) or Port (4).
• URL: the URL or IP being watched, commonly {{ $json.domain }} when it comes from a form or a sheet.

Erases a monitor from the account along with its place in the dashboard. Treat it as final, and gate it behind a condition rather than wiring it straight to a list operation.

• ID: the identifier of the monitor to remove.

Fetches a single monitor by identifier and returns its configuration to the workflow.

• ID: the identifier of the monitor, stored earlier or read from a previous node as {{ $json.id }}.

The richest read in the node: it lists monitors and lets you decide how much detail each one carries.

• Return All and Limit: all monitors, or a capped batch.
• Monitor IDs: in Filters, identifiers joined by dashes, as in 15830-32696-83920.
• Statuses and Types: multi-selects, for instance Down (9) only, or Keyword monitors only.
• Search: a keyword matched against URL and friendly name.
• Alert Contacts, Logs, Maintenance Window, Response Times: booleans that attach extra data to each monitor.

Sends a reset call for one monitor. The node asks for nothing beyond its identifier, which makes it easy to wire at the end of a branch.

• ID: the identifier of the monitor to reset.

Edits an existing monitor in place. This is the operation with the widest reach, ten fields in Update Fields, and the one to use for pause and resume.

• ID: the identifier of the monitor, the only required field.
• Status: Pause (0) or Resume (1).
• Interval: the interval for the monitoring check.
• URL, Friendly Name, Port, Sub Type: what is watched, including HTTP (80), HTTPS (443) or a Custom Port (99).
• HTTP Method, HTTP Auth Type, HTTP Username, HTTP Password: for password-protected pages.

Builds a public status page from a set of monitors and returns it, which is what turns a monitor creation workflow into a client-facing deliverable.

• Friendly Name: the name of the status page.
• Monitor IDs: the monitors displayed on it, separated with a dash, or 0 for all monitors.
• Custom Domain: in Additional Fields, the domain or subdomain the page runs on.
• Password: in Additional Fields, to keep the page semi-private.
• Sort: friendly name A to Z (1) or Z to A (2), status up first (3) or down first (4).

Once a status page has served its purpose, this operation removes it from the account. Since the catalogue has no update operation for this resource, delete and recreate is also how you change the monitors a page shows.

• ID: the identifier of the public status page.

Reads one status page back and returns its configuration, monitors and settings included.

• ID: the identifier of the public status page to read.

Enumerates the status pages on the account, one item per page, so a workflow can reconcile them against whatever list of clients you consider authoritative.

• Return All: on for the complete set, off to stop at Limit.
• Limit: how many status pages come back.
• Public Status Page IDs: in Filters, identifiers separated with a dash, as in 236-1782-4790.