--- title: "UptimeRobot Integration" description: "Monitor uptime and manage alerting from your flows over the UptimeRobot API v2. Create HTTP, Keyword, Ping, Port, and Heartbeat monitors, manage alert contacts, maintenance windows, and status pages." url: https://flowrunner.ai/integrations/uptimerobot date_modified: 2026-08-01T02:40:32-07:00 --- # UptimeRobot [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Monitor uptime and manage alerting from your flows over the UptimeRobot API v2. Create HTTP, Keyword, Ping, Port, and Heartbeat monitors, manage alert contacts, maintenance windows, and status pages. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 15 actions · API key · available [UptimeRobot website](https://uptimerobot.com/) · [Platform Documentation](https://uptimerobot.com/api/) · Capability data verified 2026-07-14 1. A new service is deployed and a flow picks up the event 2. Agent reads the endpoint URL and the monitor type it needs 3. Agent calls Create Monitor for the new endpoint 4. Agent attaches the right alert contacts so outages reach the on-call rotation 5. Agent posts the monitor's status and share URL to the team channel 6. An engineer confirms before the agent deletes a monitor during cleanup ## What This Integration Enables FlowRunner agents use UptimeRobot to keep monitoring in step with the services it watches. An agent can create and configure monitors for new endpoints as they go live, pause or resume monitors and adjust check intervals during planned changes, and manage alert contacts and attach them to monitors. It can schedule maintenance windows to suppress alerts during known downtime, and build and update shareable public status pages. The monitor type is fixed at creation, so the agent edits settings or recreates rather than changing type. What it does not do on its own is delete a monitor, because a delete drops the monitor's history and stops watching the endpoint. That confirmation stays with a person. ### Without FlowRunner **Endpoints unmonitored**: A new service ships and nobody adds a monitor for it **Alert noise in changes**: Planned downtime pages the on-call rotation because no window was set **Risky cleanup**: Someone deletes a monitor and loses the uptime history behind it ### With FlowRunner **Monitors on deploy**: The agent creates a monitor as each service goes live **Windows around changes**: The agent schedules a maintenance window to suppress expected alerts **Confirmed deletes**: Deleting a monitor waits for an engineer to confirm ## Use Case Scenarios ### Monitor on deploy A new service ships. The agent calls Create Monitor for its endpoint, chooses the right type, and attaches the alert contacts for the on-call rotation. It posts the monitor's status and share URL to the team channel. Every service that goes live is watched from the moment it ships, without an engineer adding it by hand. ### Outages into pages On a schedule, the agent calls Get Monitors filtered to the down status. For each outage, it opens an incident in the on-call tool so the responder sees it, and for a wider audience it escalates to a distribution list by email. A down endpoint reaches a person through the channels they already watch. ### Maintenance windows around planned changes A planned change is about to start. The agent calls Create Maintenance Window on the affected monitors to suppress the expected alerts, and removes the window when the change is confirmed healthy. Expected downtime stays quiet, and real outages still page. ## Human-in-Loop Highlight The human-in-loop moment in UptimeRobot is the monitor deletion gate. Creating monitors, scheduling maintenance windows, and pausing or resuming checks are all reversible, so the agent runs them by rule. Deleting a monitor is not, because it drops the monitor's uptime history and stops watching the endpoint entirely, and a silently unwatched endpoint can be down for hours before anyone notices. When a cleanup flow flags monitors for retired services, the agent lists them and asks in the operations channel: "These three monitors point at endpoints that no longer resolve. Confirm which to delete?" An engineer confirms. Only then does the agent call Delete Monitor. The agent keeps monitoring in step with the services on its own. A person owns the delete that stops the watch. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 15 actions ### Monitors 5 - **Get Monitors** List monitors, filtered by status. Used to find the monitors that are down. - **Create Monitor** Create a monitor for an endpoint. Supports HTTP(S), Keyword, Ping, Port, and Heartbeat types. - **Edit Monitor** Update a monitor's settings, or pause and resume it with the Status field. The type cannot be changed after creation. - **Delete Monitor** Delete a monitor. Drops its history and stops watching the endpoint, so run it behind a human confirmation. - **Reset Monitor** Reset a monitor's statistics. ### Alert Contacts 3 - **Get Alert Contacts** List the alert contacts in the account. - **Create Alert Contact** Add an alert contact, such as an email, SMS, or webhook. - **Delete Alert Contact** Delete an alert contact. ### Maintenance Windows 3 - **Get Maintenance Windows** List the maintenance windows. - **Create Maintenance Window** Schedule a maintenance window to suppress alerts during known downtime. - **Delete Maintenance Window** Delete a maintenance window. ### Public Status Pages 3 - **Get Public Status Pages** List the public status pages. - **Create Public Status Page** Create a shareable public status page for selected monitors. - **Delete Public Status Page** Delete a public status page. ### Account 1 - **Get Account Details** Retrieve account details. Used as a connection check. ## Frequently Asked Questions ### What can FlowRunner do with UptimeRobot? FlowRunner agents can run Get Monitors, Create Monitor, and Edit Monitor in UptimeRobot, plus 12 more actions. ### Does connecting UptimeRobot to FlowRunner require OAuth? No. UptimeRobot connects to FlowRunner with an API key, no OAuth flow required. ### Can UptimeRobot trigger a FlowRunner workflow automatically? UptimeRobot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at UptimeRobot?** This integration exposes UptimeRobot to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/uptimerobot. Site index: https://flowrunner.ai/llms.txt