UptimeRobot is a service that monitors the uptime and performance of websites, applications, and services, providing real-time alerts and detailed logs.
UptimeRobot is a service that monitors the uptime and performance of websites, applications, and services, providing real-time alerts and detailed logs. On Nagent, Uptimerobot is exposed as a fully-configurable server monitoring integration that any agent can call — 15 actions, and API key authentication. No code is required to wire Uptimerobot into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Uptimerobot to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Uptimerobot into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Uptimerobot, with input parameters and output schema. Drop these into any step of an agent built in Helix.
UPTIMEROBOT_ADD_MONITORTool to create a new monitor. Use when you need to start monitoring a URL or service; call after obtaining a valid API key.
Input parameters
Enable SSL validation: 1=yes, 0=no
URL or IP address to monitor
Port number for custom port monitors (subtype=99)
Type of monitor: 1=HTTP(s), 2=Keyword, 3=Ping, 4=Port
Port-monitor subtype if type=4: 1=HTTP,2=HTTPS,3=FTP,4=SMTP,5=POP3,6=IMAP,99=Custom
Request timeout in seconds (1-60, default=30)
Monitoring interval in minutes (min 30 for free plan, default varies by plan)
Comma-separated maintenance window IDs
For keyword monitors (type=2): 1=exists,2=not exists
User-friendly name for the monitor
Password for HTTP authentication
Username for HTTP authentication
Keyword to monitor on the page for type=2
Comma-separated IDs of alert contacts
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_DELETE_MONITORTool to delete a monitor. Use when you need to remove an existing monitor by its ID; use after confirming the monitor ID.
Input parameters
The ID of the monitor to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_EDIT_MAINTENANCE_WINDOWTool to edit an existing maintenance window. Use when you need to update its name, timing, recurrence, or duration after confirming the window ID.
Input parameters
ID of the maintenance window to edit.
Type of maintenance window: 1=once, 2=daily, 3=weekly.
Comma-separated day numbers for daily (2) or weekly (3); not needed for once (1).
Duration of the maintenance window in minutes.
Start time: 'YYYY-MM-DD HH:mm:ss' for once, 'HH:mm' for recurring or Unix timestamp in seconds.
A friendly name for the maintenance window.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_EDIT_MONITORTool to edit an existing monitor. Use after confirming the monitor ID exists.
Input parameters
ID of the monitor to be edited (required)
Enable SSL notifications: 1=Yes,0=No
New URL to be monitored
Port number for type=4 monitors
Monitor type: 1=HTTP(s),2=Keyword,3=Ping,4=Port,5=Heartbeat,6=SSL
Subtype for port monitoring if type=4
Timeout in seconds before a check is considered failed
Monitoring interval in minutes
POST data type: 1=Raw,2=URL-encoded
Ignore SSL errors: 1=Yes,0=No
POST data payload content
Verify SSL certificate: 1=Yes,0=No
HTTP method to use for monitor checks
Keyword check type: 1=Exists,2=Not Exists
New friendly name for the monitor
Password for HTTP authentication
Username for HTTP authentication
Keyword value to check in keyword monitors
Comma-separated alert contact IDs
Custom HTTP headers as a dict; will be JSON-encoded
Comma-separated maintenance window IDs
Uptime threshold percentage (0-100) for 'UP' status
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_EDIT_PUBLIC_STATUS_PAGETool to edit an existing public status page. Use after confirming the page ID. Updates friendly name, monitor set, domain, and status options in one call.
Input parameters
The unique integer ID of the public status page to edit.
Order in which monitors appear: 1=A–Z, 2=Z–A, 3=Up–Down–Paused, 4=Down–Up–Paused.
0=Paused, 1=Active. Use to enable or disable the public page.
Dash-separated list of monitor IDs to include on the page, e.g. '123-456-789'. Use '0' to include all monitors.
Password to protect the status page (if enabled).
Custom domain or subdomain where the status page will be hosted.
New friendly name for the status page. Leave blank to keep current name.
If true, removes the UptimeRobot link from the status page (Pro plan only).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_ACCOUNT_DETAILSTool to retrieve account details. Use after authenticating with a valid API key to fetch account metrics.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_ALERT_CONTACTSTool to retrieve all alert contacts configured for the account. Use when you need to list available notification channels.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_MAINTENANCE_WINDOWTool to retrieve a specific maintenance window by ID. Use when you need to get detailed information about a single maintenance window.
Input parameters
ID of the maintenance window to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_MAINTENANCE_WINDOWSTool to retrieve maintenance windows. Use after confirming a valid API key.
Input parameters
Maximum number of records to return (default: 50, max: 50).
Pagination offset; record to start returning from (default: 0).
Hyphen-separated list of maintenance window IDs to retrieve (e.g., '12345-67890'); if omitted, returns all windows. Single ID can also be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_MONITORSTool to fetch monitor details and status. Use after confirming account connection.
Input parameters
1 to include up to 21 log entries, 0 to omit.
Field by which to sort results.
Maximum number of monitors to return (max 50).
Hyphen-separated monitor type codes, e.g. '1-2'.
Zero-based pagination offset.
Search term for friendly_name, URL, or type.
Hyphen-separated monitor IDs to retrieve, e.g. '1234-5678'.
Hyphen-separated monitor status codes, e.g. '2-8'.
1 to include alert contact details, 0 to omit.
1 to include response time data, 0 to omit.
Hyphen-separated date ranges (YYYY-MM-DD_YYYY-MM-DD), e.g. '2023-01-01_2023-01-07'.
Hyphen-separated days for custom uptime ratios, e.g. '7-30-45'.
Maximum number of response time records per monitor.
UNIX timestamp (seconds) to end response time data.
Hyphen-separated day intervals for total uptime durations, e.g. '30-60-90'.
UNIX timestamp (seconds) to start response time data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_GET_PUBLIC_STATUS_PAGESTool to retrieve public status pages. Use after confirming API credentials to list all public status pages for an account. Supports pagination.
Input parameters
Maximum number of public status pages to return (1-50)
Pagination start offset; must be non-negative
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_LIST_INTEGRATIONSTool to list all integrations. Use to retrieve configured integrations for the account.
Input parameters
Cursor to paginate through the integrations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_LIST_PSPSTool to list public status pages using the v3 API. Use to retrieve all PSPs with cursor-based pagination.
Input parameters
Cursor to paginate through PSPs. Omit for first page, then use the cursor from the response to fetch subsequent pages.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_NEW_MAINTENANCE_WINDOWTool to create a new maintenance window. Use after confirming window parameters.
Input parameters
Day of the week for weekly windows (1=Monday to 7=Sunday); required if type=3.
Type of maintenance window: 1=once, 2=daily, 3=weekly.
Duration of the maintenance window in minutes.
Comma-separated monitor IDs to apply the window to; if omitted, applies to all monitors.
Start time as Unix timestamp in seconds.
User-friendly name for the maintenance window.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
UPTIMEROBOT_NEW_PUBLIC_STATUS_PAGETool to create a new public status page. Use when you want to publish a public status page for selected monitors after specifying a friendly name.
Input parameters
Sorting mode: 0=no sorting, 1=by status, 2=custom order
Page status: 0=paused, 1=active
Comma-separated IDs of monitors to display, or '*' for all monitors
Password for viewing the status page
Custom URL slug for the status page
User-assigned friendly name for the status page
Comma-separated custom domains for the status page
Hide monitor URL links: 1=yes, 0=no
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 54 agents privately built on Nagent that already use Uptimerobot.
Build on Nagent
Connect Uptimerobot to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Uptimerobot, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Uptimerobot is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Uptimerobot is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Uptimerobot steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Uptimerobot event fires, the agent kicks off automatically.
Every Uptimerobot action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Uptimerobot ships with 15 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Uptimerobot together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Uptimerobot-based workflows tailored to your business.