UptimeRobot

Connect UptimeRobot with its Read-only API key so CloudThinker can report down monitors, uptime history, and recent incidents.

Connect UptimeRobot and ask CloudThinker which monitors are down right now, what a monitor’s uptime was last week, or which incidents hit yesterday. The connection uses UptimeRobot’s Read-only API key, which can’t create, change, or pause monitors, so CloudThinker can only look.

Prerequisites

• An UptimeRobot account that owns the monitors you want CloudThinker to read.
• A Read-only API Key from that account’s Integrations & API page.
• The Admin role in the CloudThinker workspace, which you need to add connections. See Roles.

Use the Read-only API key, never the Main API key. The Main key has the same permissions as your UptimeRobot account. CloudThinker doesn’t check which key you paste. With a Main key it still runs only the three reads below, but the stored key could change your account if it ever leaked.

Setup

1. Open Integrations & API

   Sign in to UptimeRobot and go to Integrations & API.

2. Copy the Read-only API key

   Copy the Read-only API Key. Skip the Main API Key on the same page. If no Read-only key exists yet, create one there first, then copy it.

3. Add the connection in CloudThinker

   In the sidebar, click More → Workspace settings → Connections, stay on the Builtin Connections tab, and select UptimeRobot. Paste the key into UPTIMEROBOT_READ_ONLY_API_KEY, and click Connect.

   Success state: the UptimeRobot card shows Connected.

Connection details

Field	Required	Description	Example
UPTIMEROBOT_READ_ONLY_API_KEY	Yes	The Read-only API Key from Integrations & API, not the Main API Key	<your-read-only-key>

There’s no region or URL to enter.

Required permissions

The Read-only API key is the whole credential, and it’s already least privilege: it can read monitors, their statistics, and incidents, and can’t create, change, pause, or delete anything in UptimeRobot.

If an UptimeRobot account can see more monitors than CloudThinker should report on, create the Read-only key from an account scoped to those monitors instead.

Agent capabilities

CloudThinker allows three UptimeRobot reads on this connection: list monitors, get monitor stats, and list incidents. It combines them into these answers:

Capability	What you get
Account health	Monitors that are down or paused, plus recent incidents, for a time window
Monitor inventory	Your monitors with their status and overall health
Uptime and response time	Uptime statistics and response-time values over a time range
Incident summary	Recent incidents with their status and timing

By default CloudThinker looks at the last 24 hours and returns up to 10 items, and you can ask for up to 25. When a list is cut short, CloudThinker says so.

CloudThinker leaves out monitor settings, custom headers, incident logs, alert contacts, and integration details. It can’t read incident details or your integrations list, because those can expose contacts and webhook URLs.

Verify the connection

Check UptimeRobot for the last 24 hours and summarize monitors that are down or paused and any recent incidents

Success state: you get a short health summary that matches your UptimeRobot dashboard. An empty incident list is a valid answer, not an error.

Example prompts

Which UptimeRobot monitors are down right now?
What was the uptime of my API monitor over the last 7 days?
List yesterday's UptimeRobot incidents and which monitors they affected

Troubleshooting

The key is rejected

The key is wrong or has extra characters. Check for spaces around the pasted value and confirm you copied the Read-only API Key from Integrations & API. If it still fails, generate a new Read-only key in UptimeRobot and update the connection.

Health shows as unavailable

The uptime statistics read failed, so CloudThinker reports health as unavailable instead of guessing. Ask again. If UptimeRobot returned a 429, wait at least 60 seconds first.

I pasted the Main API key

Replace it. Copy the Read-only API Key from Integrations & API, open the UptimeRobot connection in More → Workspace settings → Connections, and update the key. To be safe, regenerate the Main key in UptimeRobot afterward.

429 Too Many Requests

UptimeRobot limits requests per rolling 60-second window, based on your plan. Every tool using your account’s API shares that limit. Wait 60 seconds, then ask a narrower question.

CloudThinker can't pause or change a monitor

That’s by design. The Read-only key can’t make changes, and CloudThinker doesn’t try. Make the change in UptimeRobot.

Security

• Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
• Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
• Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
• Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.

• Never use the Main API key: it carries the same permissions as your UptimeRobot account.
• Shared rate limit: other tools on the same account draw from the same request quota.

Related

Incident response (Resolve)

Turn alerts into investigated incidents

Better Stack

Add uptime, on-call, and log search