Menu

Mattering Automations UptimeRobot integration

Connect UptimeRobot to Mattering Automations: monitors with bulk pause and start, uptime and response-time statistics, incidents and comments, maintenance windows, alert contacts, channel integrations, groups, tags and status page announcements as workflow steps, authenticated with one API v3 token.

The Mattering Automations UptimeRobot integration puts UptimeRobot API v3 on your automation canvas: monitors with create, update, delete, pause, start, reset and bulk operations by group or tag; uptime statistics per monitor and account-wide; response-time series per monitor and per region; incidents with their activity log, sent alerts and comments; maintenance windows; personal and organization alert contacts; channel integrations; monitor groups; tags; and public status pages with the full announcement surface including pin and unpin. 56 nodes, 26 that read and 30 that act.

The credential is a single API token created in the UptimeRobot dashboard under Integrations & API and sent as an Authorization Bearer header. There is nothing else to fill in: v3 has no account id, no version header and no second secret. Paste the raw token and the Bearer prefix is added for you, which matches UptimeRobot's own instruction to enter the token without it.

Build against v3, not the legacy v2 API. They are two different APIs wearing one brand: v2 is POST-only for every operation including reads, with the key in the request BODY and verb-shaped paths, so an example copied from an older integration will fail completely. UptimeRobot's v3 announcement says v2 remains available but no longer receives support or updates, with new features going to v3 only, and publishes no sunset date, so treat v2 as frozen rather than retiring.

Before you start

  • An UptimeRobot account. The API is included across all plans according to UptimeRobot's own API page, from Free to Enterprise, with no separate API charge, so a free account can connect this and run the read nodes.
  • An API token, created in the dashboard under Integrations & API.
  • Awareness of which node families your plan gates, because several answer 403 rather than a clear plan message. UptimeRobot's API specification describes monitor GROUPS as a feature that may not be available on your plan, annotates monitor CUSTOM FIELDS as paid plans only, and annotates the Threshold and Recurrence settings on alert contacts as available only in the paid plans and always zero on the Free Plan. A 403 on those is a plan result, not a broken credential.
  • A check interval you are allowed to use. Interval is REQUIRED when a monitor is created and a value below your plan's floor is rejected by the API. UptimeRobot's API page states the free tier as up to 50 monitors with 5-minute monitoring intervals; confirm the current numbers on UptimeRobot's pricing page.
  • At least one monitor already set up, or the intent to create one. UptimeRobot: Create Monitor works from the canvas, and the verify path below reads cleanly on an empty account.
  • A Mattering workspace with access to the Automations app.

Create an UptimeRobot API token

UptimeRobot API v3 uses one bearer token for everything. Every documented operation declares the same security scheme, so there is nothing to scope at creation and no second secret to pair it with. The one thing to get right is that the token is a v3 token used as a header, not a v2 key placed in a request body.

Sign in to UptimeRobot and open Integrations & API.
Create an API token and copy the value.
Paste the raw token. UptimeRobot's own note says to enter it without the Bearer prefix, because the prefix is added automatically, and this integration does exactly that. Adding it yourself produces a token that is rejected for a reason the error message will not make obvious.
This token reaches your whole UptimeRobot account, including the nine destructive nodes and the pause nodes that stop monitors alerting. Treat it as a production credential and gate the write nodes in your workflows rather than relying on the token to limit them.

Connect UptimeRobot to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose UptimeRobot from the list.
Click Create new credential, paste the token into Token, and save.
The token is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls UptimeRobot's monitor list endpoint, which takes no parameters and has no side effect, so a response proves the token even on an account with no monitors yet. This works because v3 reads are ordinary GETs; the same read on v2 is a POST with the key in the body, which is one more reason not to reuse a v2 credential here.
Click Connect. All 56 UptimeRobot nodes appear in your canvas palette.

Verify it works

Open any automation canvas and check the palette: an UptimeRobot section should list the read and action nodes. Drop UptimeRobot: List Monitors onto the canvas and run a test step. It is the natural probe and the source of most other configuration: the monitor picker on eleven other nodes reads from it, grouped by CHECK TYPE (which matters, because a heartbeat monitor has no URL and a port monitor needs a port) and described by the URL each monitor checks, so two monitors sharing a friendly name are still distinguishable.

Now read a statistic, because that half has its own rules. Drop UptimeRobot: Get Monitor Uptime Stats onto the canvas, pick a monitor, and set a window inside 90 days, which is UptimeRobot's documented maximum range. The response describes the WHOLE window: uptime percentage, total downtime seconds, incident count and mean time between failures, with no per-day rows inside it.

Finally, check the incident surface. Drop UptimeRobot: List Incidents onto the canvas and run it. On a healthy account this returns an empty list, which is a pass. Note the field to test on for later: an ongoing incident carries a null resolution timestamp and a null duration that both fill in when it resolves, so poll on the resolution timestamp rather than on status text.

Everything in this verify path is read-only. It does not touch the nine destructive nodes and, just as importantly, it does not touch the pause nodes, which are not flagged destructive but do stop a monitor being checked.

Node reference

56 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 26

UptimeRobot: Get Account

uptimerobot_get_account

Get the account behind the API token: name email how many monitors exist how many the plan allows remaining SMS credits and the active subscription. Use monitorsCount against monitorLimit before a create-monitor step so a workflow can stop rather than fail on a plan limit.

UptimeRobot: Get Account Uptime Stats

uptimerobot_get_account_uptime_stats

Account-wide uptime across every monitor for a timeframe plus a log of the downtime and slow-response entries behind it. This is the closest thing v3 has to the old monitor-logs call: the logs array carries each entry's type timestamp and duration. Pick a preset timeframe or send CUSTOM with a start and end Unix timestamp. Note that overall uptime is a percentage across the whole window so it cannot be added up across windows.

UptimeRobot: Get Alert Contact

uptimerobot_get_alert_contact

Get one personal alert contact with its type destination value which monitor events it is notified for whether SSL expiry reminders are on and whether it is active. A contact that is not Active has not completed verification and will not receive anything.

UptimeRobot: Get Incident

uptimerobot_get_incident

Get one incident with its root-cause detail: what failed the reason text the status the start and resolve times and the duration. Use it after UptimeRobot: List Incidents when you need the diagnosis rather than the summary row.

UptimeRobot: Get Incident Activity Log

uptimerobot_get_incident_activity_log

The full timeline of one incident newest first: every status change with the region and checking node that observed it every comment and every notification. Rows differ by their type field so a STATUS_UPDATE row carries region and responseTime while a COMMENT row carries the comment. This is what to paste into a postmortem.

UptimeRobot: Get Incident Sent Alerts

uptimerobot_get_incident_alerts

Every alert UptimeRobot sent for one incident: who it went to which channel it used when it left and whether delivery succeeded. A NOT_DELIVERED row is the answer to why nobody reacted so this is the node an escalation workflow checks before assuming the team was told.

UptimeRobot: Get Integration

uptimerobot_get_integration

Get one notification channel with its type destination custom values and status. The meaning of the customValue fields depends on the channel type - a Slack integration puts the target channel there while a webhook uses them for its payload settings.

UptimeRobot: Get Maintenance Window

uptimerobot_get_maintenance_window

Get one maintenance window: its repeat interval start date and time duration in minutes which days it runs on whether new monitors are added automatically and which monitors it currently covers.

UptimeRobot: Get Monitor

uptimerobot_get_monitor

Get one monitor's full configuration and current state: status check interval timeout regions assigned alert contacts tags custom fields SSL and domain expiry dates and the last 24 hours of uptime. Use this to read a monitor before updating it so an update only changes what you meant to change.

UptimeRobot: Get Monitor Group

uptimerobot_get_monitor_group

Get one monitor group by id with its name and timestamps. To see which monitors are in it use UptimeRobot: List Monitors with the same group_id filter - the group record itself does not carry its members.

UptimeRobot: Get Monitor Response Times

uptimerobot_get_monitor_response_times

Minimum maximum and average response time in milliseconds for one monitor over a date range plus how many measurements those figures came from. Defaults to the last 24 hours and the API caps a single request at 90 days. Turn on include_time_series to also get every individual measurement with its timestamp which is what a chart needs. Optionally narrow to one monitoring region.

UptimeRobot: Get Monitor Response Times By Region

uptimerobot_get_monitor_response_times_by_region

The same response-time figures split by monitoring region in one call: separate min max average and measurement count under na eu as and oc. Use it to see whether a slowdown is global or regional. The payload is keyed BY REGION rather than being a list so downstream paths name a region directly - data.na.summary.avg - and a region the monitor does not check comes back null.

UptimeRobot: Get Monitor Uptime Stats

uptimerobot_get_monitor_uptime_stats

Uptime percentage total downtime incident count and mean time between failures for one monitor over a date range. Defaults to the last 24 hours and the API caps a single request at 90 days. The answer describes the WHOLE window as one figure: there are no per-day rows so the uptime percentage cannot be added up or averaged across windows without a denominator the API does not return. Read it per window you actually want to report on.

UptimeRobot: Get Status Page

uptimerobot_get_status_page

Get one public status page with its url key custom domain covered monitor ids and tag ids pinned announcement and the full custom-settings block covering theme colours fonts and which widgets are shown.

UptimeRobot: Get Status Page Announcement

uptimerobot_get_announcement

Get one status page announcement with its title body type start and end dates publication status subscriber delivery status and sent count.

UptimeRobot: List Alert Contacts

uptimerobot_list_alert_contacts

List the personal alert contacts the API token's own user owns: email addresses Pro SMS numbers voice calls and mobile push devices with each one's type value and activation status. Channel integrations like Slack and webhooks live separately under UptimeRobot: List Integrations. This is the node that populates alert-contact pickers.

UptimeRobot: List All Alert Contacts

uptimerobot_list_all_alert_contacts

Every alert contact reachable from this account grouped by the user who owns it: the token holder's own contacts notify-only contacts and each active organization member's contacts. Use it to audit who gets paged across a team. Note the response is a BARE ARRAY so rows are at data[] rather than data.data[] and each row nests its contacts under alertContacts.

UptimeRobot: List Incident Comments

uptimerobot_list_incident_comments

Comments on one incident oldest first with who wrote each one and whether it is published on the public status page. Use it to build an incident timeline or to find the comment id an update or delete needs.

UptimeRobot: List Incidents

uptimerobot_list_incidents

List downtime and slow-response incidents across the account with the monitor that raised each one why it fired when it started and how long it lasted. Filter by monitor by name or by start date range. An incident that is still ongoing has a null resolvedAt and a null duration - both fill in when it resolves - so a workflow polling for open incidents should key on resolvedAt being null rather than on status text.

UptimeRobot: List Integrations

uptimerobot_list_integrations

List the notification channels wired to this account: Slack Discord Telegram Microsoft Teams Google Chat Mattermost Splunk PagerDuty Pushover Pushbullet Zapier and plain webhooks. Each row carries its id friendly name type destination and whether it fires on up down or both. Integration ids are what assigned_alert_contacts on a monitor accepts alongside personal contact ids.

UptimeRobot: List Maintenance Windows

uptimerobot_list_maintenance_windows

List the account's maintenance windows with their schedule duration status and the monitors each one covers. Alerts are suppressed for those monitors while an active window is running so this is where to look when an expected alert never arrived.

UptimeRobot: List Monitor Groups

uptimerobot_list_monitor_groups

List the account's monitor groups with their ids names and timestamps. Groups are how the bulk pause start and update nodes select what to act on. Note the built-in default group for ungrouped monitors is id 0 and is NOT returned here - send 0 explicitly when a node needs it.

UptimeRobot: List Monitors

uptimerobot_list_monitors

List the monitors on the account with their current status interval and configuration. Filters combine with AND logic. This is the node every other UptimeRobot node leans on: monitor pickers are populated from it and it is the cheapest way to confirm a credential works.

UptimeRobot: List Status Page Announcements

uptimerobot_list_announcements

List a status page's announcements newest first with each one's title body type schedule publication status and how many subscribers it reached. Filter by status to separate drafts from what customers can actually see right now.

UptimeRobot: List Status Pages

uptimerobot_list_status_pages

List the account's public status pages with each one's url key custom domain covered monitors password state and styling. The public address is built from the url key so this is how an automation finds the link to share during an incident.

UptimeRobot: List Tags

uptimerobot_list_tags

List the account's monitor tags with their ids and names sorted by id. Tags are what the bulk nodes filter on and what the monitor lister's tags filter matches by NAME. Note this endpoint pages with nextCursorId rather than the nextLink the other list endpoints return.

Action nodes 30

UptimeRobot: Create Alert Contact

uptimerobot_create_alert_contact

Create a personal alert contact. Email and mobile push are the types this endpoint can create; Pro SMS and voice need phone verification in the dashboard and are rejected here. A new email contact is not usable until the recipient confirms it so expect the status to come back as something other than Active and do not assign it to a monitor and assume alerts will arrive.

UptimeRobot: Create Incident Comment

uptimerobot_create_incident_comment

Add a comment to an incident and optionally publish it on the public status page. This is how an automation narrates an outage: post what is known when the incident opens then post the resolution when the monitor recovers. Publishing puts the text in front of customers so treat that flag as a public statement.

UptimeRobot: Create Integration

uptimerobot_create_integration

Wire up a notification channel. The type picks the shape of the data object so a Slack integration wants a webhook URL and a channel while a plain Webhook integration wants a URL and a payload template. The new integration's id is what assigned_alert_contacts on a monitor accepts. Nothing is verified at creation time so a wrong webhook URL fails silently at the first alert - test it with a monitor you can safely pause and start.

UptimeRobot: Create Maintenance Window

uptimerobot_create_maintenance_window

Schedule a maintenance window that suppresses alerts for the monitors it covers. Choose a one-off or a daily weekly or monthly repeat then give it a start date a start time and a duration in minutes. Weekly and monthly repeats also need the days list. Creating the window does not pause the monitors: they keep being checked and the history stays continuous - only the alerting is held back.

UptimeRobot: Create Monitor

uptimerobot_create_monitor

Create a monitor of any of the nine supported types. The type field decides which of the other fields apply: HTTP and KEYWORD check a URL, PING and PORT check a host, HEARTBEAT waits for an inbound check-in, DNS compares records, API asserts on a JSON response, UDP sends a payload, and VISUAL_COMPARISON watches a page for visual change. How many monitors an account may hold and how low the interval may go are both capped by the UptimeRobot plan, so a rejected create is usually a plan limit rather than a bad request.

UptimeRobot: Create Monitor Group

uptimerobot_create_monitor_group

Create a monitor group and optionally fill it straight away either by listing monitor ids or by naming existing groups whose monitors should MOVE into the new one. A monitor belongs to exactly one group so both forms move monitors rather than copying them. Monitor groups are documented as a plan-gated feature and the API answers 403 when the account does not have it.

UptimeRobot: Create Status Page Announcement

uptimerobot_create_announcement

Post an announcement to a public status page: a maintenance notice an incident update or general information. Setting status to Published makes it CUSTOMER VISIBLE immediately and can send it to the page's subscribers so draft with Offline or schedule with Pending when the wording still needs a human. This is the outward-facing half of an incident automation - UptimeRobot: Create Incident Comment is the internal half.

UptimeRobot: Delete Alert Contact

uptimerobot_delete_alert_contact

DESTRUCTIVE. Removes a personal alert contact permanently and with it every assignment to a monitor - those monitors simply stop notifying this destination and nothing warns you. There is no trash and no undo and a recreated email contact has to be verified again before it works. To take a contact off call temporarily set is_active false with UptimeRobot: Update Alert Contact instead.

UptimeRobot: Delete Incident Comment

uptimerobot_delete_incident_comment

DESTRUCTIVE. Removes a comment from an incident permanently - UptimeRobot has no trash and no undo so the text is gone. If the comment was published on the status page it disappears from the public timeline too which can leave a customer-visible gap in the incident narrative. Prefer UptimeRobot: Update Incident Comment to correct a comment rather than deleting it.

UptimeRobot: Delete Integration

uptimerobot_delete_integration

DESTRUCTIVE. Removes a notification channel permanently along with every monitor assignment that pointed at it. Those monitors stop notifying that channel immediately and nothing warns you - the failure looks like an outage nobody was told about. There is no trash and no undo and recreating the channel means re-assigning it to every monitor by hand.

UptimeRobot: Delete Maintenance Window

uptimerobot_delete_maintenance_window

DESTRUCTIVE. Removes a maintenance window permanently - UptimeRobot has no trash so the schedule and its monitor assignments are gone and the id stops resolving anywhere it was referenced. Alerts that the window was suppressing start firing again straight away. To silence a window temporarily set its status to paused with UptimeRobot: Update Maintenance Window instead.

UptimeRobot: Delete Monitor

uptimerobot_delete_monitor

DESTRUCTIVE and irreversible. Deleting a monitor takes its entire history with it: every incident every response-time measurement and every uptime figure ever recorded for it. UptimeRobot documents no trash and no restore anywhere in v3 so there is no way to get any of it back. If you only want the checks to stop use UptimeRobot: Pause Monitor which keeps the history.

UptimeRobot: Delete Monitor Group

uptimerobot_delete_monitor_group

DESTRUCTIVE. Removes a monitor group permanently. The monitors themselves survive and are moved to the group you name or to the default group 0 if you name none - so no monitoring is lost - but the grouping is gone with no undo and anything that selected monitors by this group id stops matching. Bulk pause and start rules pointed at this group silently select nothing afterwards. The default group 0 cannot be deleted.

UptimeRobot: Delete Status Page

uptimerobot_delete_status_page

DESTRUCTIVE and PUBLICLY visible. Removes a status page permanently: its url key stops resolving so any link a customer or a vendor questionnaire has bookmarked goes dead and its announcement history goes with it. There is no trash and no undo. Note this connector cannot recreate the page for you - creating and updating a status page are multipart file uploads the canvas cannot produce so recovery means the dashboard.

UptimeRobot: Delete Tag

uptimerobot_delete_tag

DESTRUCTIVE. Deletes a tag and strips it from EVERY monitor carrying it in one call. The monitors survive but their labelling is gone with no undo and anything selecting monitors by this tag - bulk pause rules status page filters saved searches - silently matches nothing afterwards. Check what would be affected with UptimeRobot: List Monitors filtered by the tag name first.

UptimeRobot: Pause Monitor

uptimerobot_pause_monitor

Stop checking a monitor until it is started again. Not destructive - the history is kept and the monitor resumes exactly as configured - but say it plainly: a paused monitor STOPS ALERTING so an outage while it is paused goes unreported. Idempotent: pausing an already paused monitor succeeds.

UptimeRobot: Pause Monitors In Bulk

uptimerobot_bulk_pause_monitors

Pause every monitor matching a group a tag or both. Supplying both narrows to monitors matching BOTH filters. At least one filter is required so there is no way to pause the whole account by accident. Not destructive but every matched monitor STOPS ALERTING until it is started again - the usual use is a maintenance window that a deploy pipeline opens and closes. The response reports success or error per monitor.

UptimeRobot: Pin Status Page Announcement

uptimerobot_pin_announcement

Pin an announcement to the top of a public status page so it is the first thing a visitor reads. Idempotent: pinning an already pinned announcement succeeds. A status page tracks ONE pinned announcement at data.pinnedAnnouncementId so pinning a second one replaces the first.

UptimeRobot: Reset Monitor Stats

uptimerobot_reset_monitor_stats

DESTRUCTIVE and irreversible even though nothing is deleted. The monitor keeps running but its accumulated statistics go to zero and its incidents and sent alerts are cleared. Every uptime figure and every incident record for this monitor is gone with no way to restore it. Read the numbers you need with UptimeRobot: Get Monitor Uptime Stats BEFORE running this.

UptimeRobot: Start Monitor

uptimerobot_start_monitor

Resume a paused monitor so checks and alerting start again. Idempotent: starting an already running monitor succeeds. Pair this with UptimeRobot: Pause Monitor around a deploy so the window is closed even if the deploy step fails.

UptimeRobot: Start Monitors In Bulk

uptimerobot_bulk_start_monitors

Resume every paused monitor matching a group a tag or both. Supplying both narrows to monitors matching BOTH filters and at least one is required. This is the closing half of a deploy-window automation: pause in bulk before the deploy and start in bulk after it. The response reports success or error per monitor.

UptimeRobot: Unpin Status Page Announcement

uptimerobot_unpin_announcement

Remove an announcement from the top of a public status page. The announcement itself is untouched and stays in the list. Idempotent: unpinning something that is not pinned succeeds. This is the closing step of an incident workflow - unpin once the monitor recovers.

UptimeRobot: Update Alert Contact

uptimerobot_update_alert_contact

Rename a personal alert contact change which events it hears about toggle its SSL expiry reminders or pause it. Only the fields you fill are sent. The destination itself cannot be changed here: to point alerts at a different address create a new contact. Setting is_active to false silences the contact everywhere it is assigned without deleting it which is the safe way to take someone off call.

UptimeRobot: Update Incident Comment

uptimerobot_update_incident_comment

Rewrite an existing incident comment or change whether it is published on the status page. The content field is required so send the full replacement text rather than an addition. Editing a published comment changes what customers see immediately.

UptimeRobot: Update Integration

uptimerobot_update_integration

Change an existing notification channel: rename it point it somewhere else or change which events it fires on. Send the same type the integration already has - the type selects which shape the data object is validated against and is not a way to convert a Slack integration into a webhook.

UptimeRobot: Update Maintenance Window

uptimerobot_update_maintenance_window

Change a maintenance window in place or pause and resume it. Only the fields you fill are sent. monitor_ids REPLACES the covered set rather than adding to it so send the full intended list. Setting status to paused stops the window SUPPRESSING alerts which is the opposite of pausing a monitor - a paused window means alerts get through again.

UptimeRobot: Update Monitor

uptimerobot_update_monitor

Change an existing monitor in place. Only the fields you fill are sent so everything else is left alone. Two fields do NOT merge the way the rest do: assigned_alert_contacts and tag_names REPLACE the current lists rather than adding to them so send the full intended list. The config object is a shallow merge - omit a key to keep it and set a key to null to remove it.

UptimeRobot: Update Monitor Group

uptimerobot_update_monitor_group

Rename a monitor group. Renaming is all this endpoint does - to move monitors between groups set each monitor's group_id with UptimeRobot: Update Monitor or UptimeRobot: Update Monitors In Bulk.

UptimeRobot: Update Monitors In Bulk

uptimerobot_bulk_update_monitors

Apply the same settings change to every monitor matching a group a tag or both. Only the settings you fill are changed. At least one filter is required and supplying both narrows to monitors matching BOTH. The blast radius is whatever matches at that moment so check it with UptimeRobot: List Monitors using the same filter first. The response reports success or error per monitor.

UptimeRobot: Update Status Page Announcement

uptimerobot_update_announcement

Edit an announcement or move it between states. Only the fields you fill are sent. Moving status from Offline to Published is how a draft goes live and moving it to Archived takes it off the page while keeping the history - both are immediately visible to customers. There is no delete endpoint for announcements in v3 so Archived is the intended way to retire one.

Using the integration

On the automation canvas

UptimeRobot nodes chain with every other node, which is where most of the value is. A deploy webhook can pause monitors, run the release, and resume them. A schedule can poll UptimeRobot: List Incidents, open a Mattering task, post to a channel, and write a row in one run. A new client record in another app can create the monitor that watches their site with UptimeRobot: Create Monitor. One value does most of the wiring: the monitor id, which is a picker sourced from UptimeRobot: List Monitors and searchable by name, because UptimeRobot's own list endpoint supports a case-insensitive partial match on it and a large account can hold thousands of monitors.

From AI assistants over MCP, and how this differs from UptimeRobot's own MCP server

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. UptimeRobot publishes an MCP server of its own and it is worth knowing before you choose. It is hosted by UptimeRobot with no local server to run, it is client-agnostic with ready-made setups for several editors, and it authenticates with an API token or an OAuth sign-in where you approve read-only or full access. It covers monitors and their status, recent incidents, connected integrations, monitor create and update, uptime figures, and response-time series with min, max, average and p95. For asking questions about your monitoring from a chat client, use it. This integration is the operations side of the same access: the nodes are workflow STEPS as well as assistant tools, so they run on a schedule or off a trigger with nobody present, chain with every other connector in one automation, hold the credential once in a shared workspace store rather than in each person's client config, cover a wider surface (maintenance windows, alert contacts, monitor groups, tags, incident comments and the whole status page announcement family), and flag the nine destructive nodes so you can gate them. The two are complementary rather than exclusive.

Pausing, and the rule that prevents the worst outage

This is the one paragraph to read twice. Pausing a monitor stops it being CHECKED, which means it stops ALERTING. A deploy workflow that runs UptimeRobot: Pause Monitors In Bulk and then fails before it reaches the start step leaves the account silently unmonitored, and nothing will tell you. Put UptimeRobot: Start Monitors In Bulk on the failure path as well as the success path, every time. The bulk nodes require at least one filter, a group or a tag, so there is no accidental all-monitors form, but the scope is still whatever matches at that instant rather than a list somebody checked. The word pause inverts one node family away: pausing a MAINTENANCE WINDOW stops it SUPPRESSING alerts, so a paused window means alerts get through. Same word, opposite meaning, two nodes apart. If suppression rather than stopping the checks is what you want, UptimeRobot: Create Maintenance Window is the node.

Creating and updating monitors without surprises

UptimeRobot: Create Monitor and UptimeRobot: Update Monitor carry several documented asymmetries that produce wrong results rather than errors, so they are worth knowing before a workflow depends on them. The assigned alert contacts and the tag names REPLACE on update rather than adding, so an update sending one contact removes every other contact from that monitor. The configuration object on update is a shallow merge with an escape hatch: omit a key to leave it alone, set a key to null to remove it, or send the whole object as null to clear everything. The keyword case setting changes TYPE between the two nodes, taking named strings on create and numbers on update, which is UptimeRobot's own documented asymmetry rather than a quirk here. The response-time threshold always reads back as zero even after a successful write, because the value is applied per region rather than to the scalar field, so a workflow that writes it and then asserts on the read-back will loop forever. And the regional data field is a string on the single-monitor nodes and an object on UptimeRobot: Update Monitors In Bulk, so a configuration copied between them is rejected.

Incidents, comments and status page announcements

UptimeRobot: List Incidents is what a schedule polls, and the field to test is the resolution timestamp being null: an ongoing incident has a null resolution time and a null duration, both filled in later, so testing status text is less reliable than testing that. UptimeRobot: Get Incident Activity Log and UptimeRobot: Get Incident Sent Alerts explain what happened and who was notified, and UptimeRobot: Create Incident Comment writes the human context back so UptimeRobot's timeline matches your task tracker's. On the customer-facing side, UptimeRobot: Create Status Page Announcement, UptimeRobot: Update Status Page Announcement, UptimeRobot: Pin Status Page Announcement and UptimeRobot: Unpin Status Page Announcement make the public message part of the workflow rather than something remembered under pressure. One boundary is worth stating: creating or updating the status PAGE itself is not available, because UptimeRobot declares both operations as multipart form uploads only (the schema exists to carry a logo file) and a workflow canvas cannot produce a multipart body. UptimeRobot: List Status Pages, UptimeRobot: Get Status Page and UptimeRobot: Delete Status Page are all built.

Alert contacts and integrations, and two silent failures

UptimeRobot: List Alert Contacts covers your own contacts and UptimeRobot: List All Alert Contacts is the only node that shows organization members' contacts as well. UptimeRobot: Create Alert Contact and UptimeRobot: Update Alert Contact manage them, and UptimeRobot: Create Integration and UptimeRobot: Update Integration manage channels such as Slack, Discord, Teams and webhooks. Two things fail quietly and both only show up during a real outage. A new EMAIL alert contact is not usable until it has been verified, so create returns a contact whose status is not active and assigning it to a monitor does not mean alerts will arrive. And integrations are NOT validated at creation, so a wrong webhook URL or a bad Slack hook is accepted and fails at the first alert. Test both deliberately rather than assuming. The Threshold and Recurrence settings are annotated by UptimeRobot as paid-plan only and always zero on the Free Plan.

Groups, tags and bulk scope

UptimeRobot: List Monitor Groups, UptimeRobot: Create Monitor Group, UptimeRobot: Update Monitor Group and UptimeRobot: Delete Monitor Group organise monitors, and UptimeRobot: List Tags and UptimeRobot: Delete Tag cover tags. Groups are the family most likely to answer 403 on a smaller plan, because UptimeRobot's API describes them as a feature that may not be available and returns 403 when it is not, which reads like a permission problem rather than a plan one. Two behaviours to build around. The DEFAULT group is not returned by the group lister, so a group picker cannot offer ungrouped; every group field's description names the value that means it. And tag names on monitor create and update take NAMES rather than ids, where naming a tag that does not exist CREATES it, which is why those fields are free text while the tag FILTER fields on the bulk nodes are pickers over existing tags only.

Reading statistics without producing a wrong chart

Three nodes report numbers and each has a rule. UptimeRobot: Get Monitor Uptime Stats describes a WHOLE window with no rows inside it: uptime percentage, downtime seconds, incident count, mean time between failures. Uptime is a rate and UptimeRobot returns no denominator beside it, so an average of daily uptimes is not the month's uptime and nothing in the response makes it recoverable. This integration deliberately declares no aggregation rule on these numbers so that a consumer refuses to combine them rather than combining them wrongly: re-request the window you want to report on. UptimeRobot: Get Monitor Response Times returns individual measurements at the monitor's own check interval, at irregular timestamps and with no bucketing parameter, and the endpoint has no row cap, so a one-minute monitor over 30 days is tens of thousands of points in a single execution record. UptimeRobot: Get Monitor Response Times By Region returns a payload keyed by region code, and a region the monitor does not check comes back as null rather than as a zeroed object. UptimeRobot documents a maximum range of 90 days on these, so longer histories are several requests. UptimeRobot: Get Account Uptime Stats has its own shape: it takes a time-frame mode, and the start and end dates apply ONLY when that mode is set to custom, which is why it is the one windowed node here that declares no window at all.

Pagination, and where the pattern breaks

v3 lists are cursor-paginated and return the rows alongside a next-page link, with the cursor being the id that link ends with, passed back on the next call. This integration does not follow that link automatically, so a workflow that needs every monitor loops on the cursor deliberately rather than getting a surprise page count. One endpoint breaks the pattern and it is worth knowing before you write a generic loop: UptimeRobot: List Tags pairs its rows with a next-cursor NUMBER instead of a next-page link, so a helper written against the link field will silently stop after one page there. UptimeRobot: List All Alert Contacts breaks it differently, returning a bare top-level array rather than an object, with each row nesting its contacts one level further down, which is also why that node is not a picker source anywhere.

Troubleshooting

Test Connection fails, or every node returns 401
Check the token first for whitespace picked up in the copy, and confirm it still exists in the UptimeRobot dashboard under Integrations & API. Then check for the two v3 mistakes. If you pasted the token WITH a Bearer prefix, remove it: UptimeRobot's own instruction is to enter the token without the prefix because it is added automatically, so including it produces a malformed header. If the credential came from an older integration, it may be a v2 key, which is a different thing entirely: v2 sends the key in the request BODY of a POST, and no v2-era key or flavour (account-specific, monitor-specific, read-only) is a v3 bearer token. Create a fresh token for v3.
A node returns 403 while other nodes work
Read it as a plan or permission result rather than a broken credential, because UptimeRobot uses 403 for both. Monitor GROUP endpoints answer 403 when the monitor-groups feature is not available on your plan, and the message itself mentions either write permission or feature availability. Monitor CUSTOM FIELDS are annotated by UptimeRobot as paid plans only. Several write endpoints answer 403 with a no-write-permission message, which points at a read-limited token: v3 documents one token type and no scopes, but read-limited tokens evidently still exist at the account level, so mint a fresh token rather than assuming the endpoint is broken. Confirm what your plan includes on UptimeRobot's pricing page before rebuilding the workflow around it.
Monitors stopped alerting after a deploy workflow ran
The workflow paused them and never resumed. Pausing a monitor stops it being CHECKED, which means it stops alerting, and nothing in UptimeRobot announces that the account is unmonitored. Run UptimeRobot: Start Monitors In Bulk with the same filter to recover, then fix the workflow: the start step belongs on the FAILURE path as well as the success path, so a run that dies mid-way still resumes monitoring. If suppression rather than stopping the checks was the intent, use UptimeRobot: Create Maintenance Window instead, and remember the inversion there: pausing a maintenance window stops it suppressing, so alerts get through.
A monitor update removed alert contacts or tags I did not touch
Documented behavior rather than a fault. On UptimeRobot: Update Monitor the assigned alert contacts and the tag names REPLACE rather than add, so an update sending one contact removes every other contact from that monitor, and the same applies to tags. Send the complete set you want the monitor to end up with, which usually means reading the monitor first with UptimeRobot: Get Monitor and merging your change into what it returned. The configuration object behaves differently again: it is a shallow merge where omitting a key leaves it alone, setting a key to null removes it, and sending the whole object as null clears everything, so an empty object and a null are not the same instruction.
Creating a monitor is rejected on the interval
The check interval is required at creation and a value below your plan's floor is rejected by the API. UptimeRobot's API page states the free tier as up to 50 monitors with 5-minute monitoring intervals, so a workflow templating a one-minute interval will fail on a free account and succeed on a paid one, which makes it look intermittent when it is not. Set the interval to a value your plan allows, and confirm the current numbers on UptimeRobot's pricing page. A rejection on monitor COUNT rather than interval is the same class of problem from the other direction.
A monitor writes the response-time threshold but reads back zero
Expected, and it will trap any workflow that writes then asserts. The write is applied per active region rather than to the scalar field, so the scalar always reads back as zero even after a successful update. Do not build a confirmation loop on it, because that loop never terminates. Verify by reading the regional data instead, or simply trust the successful write. A related type trap sits nearby: the keyword case setting takes named strings on create and numbers on update, and the regional data field is a string on the single-monitor nodes but an object on UptimeRobot: Update Monitors In Bulk, so a configuration copied between nodes is rejected.
Alerts never arrived for a contact or integration the workflow created
Two silent failures, both of which look fine at setup. A new EMAIL alert contact is not usable until it has been VERIFIED: create returns a contact whose status is not active, and assigning it to a monitor does not make alerts arrive. Check the contact's status with UptimeRobot: Get Alert Contact and complete the verification from the email UptimeRobot sent. Integrations are NOT validated at creation, so a wrong Slack webhook URL or a typo in a webhook endpoint is accepted and fails at the first real alert. Test the channel deliberately after UptimeRobot: Create Integration rather than assuming a successful create means a working route. If the missing settings are Threshold or Recurrence, note that UptimeRobot annotates both as paid-plan only and always zero on the Free Plan.
A loop over a list only ever sees one page
Check which lister it is. v3 lists are cursor-paginated and return a next-page LINK, and this integration deliberately does not follow it automatically, so the loop must pass the cursor back itself. UptimeRobot: List Tags breaks the pattern by returning a next-cursor NUMBER instead of a link, so a generic helper written against the link field stops after one page there and looks like a short result rather than an error. UptimeRobot: List All Alert Contacts breaks it differently again, returning a bare top-level array with each row nesting its contacts one level further down, which is why it is not a picker source for anything.
A group picker does not offer the group I expect
If the group you want is the DEFAULT one, that is expected: UptimeRobot's group lister omits it, so no picker can offer ungrouped, and every group field's description names the value that means it. If groups are missing entirely and the lister returns 403, that is the plan gate rather than the picker: UptimeRobot describes monitor groups as a feature that may not be available and answers 403 when it is not. If it is a TAG rather than a group, remember the split: tag fields on monitor create and update take NAMES and will create a tag that does not exist, so they are free text on purpose, while the tag FILTER fields on the bulk nodes are pickers over existing tags only.
An uptime figure computed from daily numbers does not match UptimeRobot
It cannot, and there is no setting that makes it match. Uptime is a percentage and UptimeRobot returns no denominator column beside it (no checks performed, no seconds observed), so daily figures cannot be weighted into a correct monthly one. This integration declares no aggregation rule on those numbers deliberately, so a well-behaved consumer refuses to combine them rather than combining them wrongly. Ask UptimeRobot: Get Monitor Uptime Stats for the exact window you want to report on. Two related shapes: downtime seconds and incident count describe the whole requested window rather than any row inside it, and UptimeRobot documents a maximum range of 90 days, so a year is several separate requests rather than one. On UptimeRobot: Get Account Uptime Stats check the time-frame mode as well: the start and end dates apply only when it is set to custom and are ignored otherwise, which produces a confidently wrong period rather than an error.

UptimeRobot is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products