> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/uptimerobot.md).

# UptimeRobot

Create and manage monitors and alert contacts with UptimeRobot.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector   | Authentication |
| ----------- | -------------- |
| UptimeRobot | Main API Key   |

### UptimeRobot

Create and manage monitors and alert contacts with UptimeRobot.

#### Set up in UptimeRobot

1. Prepare the UptimeRobot account or service that the workflow will access. Grant access to the required resources and operations.
2. **Main API Key:** Use the account-specific Main API Key from UptimeRobot. A Read-only API Key can pass the connection check but cannot create, pause, or delete monitors.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **UptimeRobot**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                                                         |
| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Main API Key  | Yes      | Use the account-specific Main API Key from UptimeRobot. A Read-only API Key can pass the connection check but cannot create, pause, or delete monitors. [Provider instructions](https://help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-integration-guide). |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **UptimeRobot** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create Monitor

Create an UptimeRobot monitor for a URL, host, port, keyword, or heartbeat endpoint.

#### Inputs

| Field           | Type            | Required | Description                                                                                                      |
| --------------- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
| Friendly Name   | string          | Yes      | A recognizable name for the monitor in UptimeRobot.                                                              |
| URL or Host     | string          | Yes      | The URL, host, or heartbeat target UptimeRobot should monitor.                                                   |
| Monitor Type    | select (string) | No       | The kind of uptime check to create. Available values: HTTP(s), Keyword, Ping, Port, Heartbeat. Default: 1.       |
| Check Interval  | integer         | No       | Seconds between checks; the account's minimum still applies. Default: 300.                                       |
| Request Timeout | integer         | No       | Seconds to wait before an HTTP, keyword, or port check times out.                                                |
| Port Subtype    | select (string) | No       | The protocol preset for a port monitor. Available values: HTTP, HTTPS, FTP, SMTP, POP3, IMAP, Custom.            |
| Port            | integer         | No       | The TCP port checked by a port monitor.                                                                          |
| Keyword Rule    | select (string) | No       | Whether the check should find or not find the keyword. Available values: Keyword exists, Keyword does not exist. |
| Keyword         | string          | No       | The text searched for by a keyword monitor.                                                                      |
| Keyword Case    | select (string) | No       | Whether keyword matching should ignore letter case. Available values: Case-sensitive, Case-insensitive.          |

#### Outputs

| Field       | Type    | Description                                        |
| ----------- | ------- | -------------------------------------------------- |
| Monitor ID  | integer | The exact identifier of the newly created monitor. |
| Status      | integer | The numeric status returned for the new monitor.   |
| Status Name | string  | A readable label for the returned monitor status.  |

### Get monitor status

Retrieve current status and core details for a monitor selected from the picker or supplied by exact ID.

#### Inputs

| Field   | Type             | Required | Description                                                                                                      |
| ------- | ---------------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
| Monitor | select (integer) | Yes      | The monitor to inspect, selected by name or supplied by its exact ID. Options load from the selected connection. |

#### Outputs

| Field         | Type    | Description                                    |
| ------------- | ------- | ---------------------------------------------- |
| Monitor ID    | integer | The exact monitor identifier.                  |
| Friendly name | string  | The monitor's display name.                    |
| URL           | string  | The target currently monitored.                |
| Type          | integer | The monitor's numeric type.                    |
| Interval      | integer | Seconds between checks.                        |
| Status        | integer | The monitor's exact numeric status.            |
| Status name   | string  | A readable monitor status label.               |
| Created at    | integer | The monitor creation time as a Unix timestamp. |

### Pause Monitor

Pause an UptimeRobot monitor so it stops checking until resumed.

#### Inputs

| Field   | Type             | Required | Description                                                                                                    |
| ------- | ---------------- | -------- | -------------------------------------------------------------------------------------------------------------- |
| Monitor | select (integer) | Yes      | The monitor to pause, selected by name or supplied by its exact ID. Options load from the selected connection. |

#### Outputs

| Field      | Type    | Description                                             |
| ---------- | ------- | ------------------------------------------------------- |
| Monitor ID | integer | The monitor identifier returned by editMonitor.         |
| Paused     | boolean | Whether the requested paused target state was accepted. |
| Status     | integer | The accepted paused target status value.                |

### Delete monitor

Permanently delete one UptimeRobot monitor.

#### Inputs

| Field   | Type             | Required | Description                                                                                                                 |
| ------- | ---------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
| Monitor | select (integer) | Yes      | The monitor to permanently delete, selected by name or supplied by its exact ID. Options load from the selected connection. |

#### Outputs

| Field      | Type    | Description                                          |
| ---------- | ------- | ---------------------------------------------------- |
| Monitor ID | integer | The exact identifier UptimeRobot reports as deleted. |
| Deleted    | boolean | Whether UptimeRobot accepted the deletion.           |

### Create Alert Contact

Create an UptimeRobot alert contact using a current, non-deprecated contact type. Plan availability varies.

#### Inputs

| Field         | Type            | Required | Description                                                                                                                                                                                                                       |
| ------------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contact type  | select (string) | Yes      | The alert channel to create; availability can depend on the UptimeRobot plan. Available values: Email, Twitter, Webhook, Pushbullet, Zapier, Pushover, Slack, Splunk, PagerDuty, Opsgenie, Microsoft Teams, Google Chat, Discord. |
| Contact value | secret          | Yes      | The email, username, webhook URL, or integration credential required by the selected contact type; it may be sensitive.                                                                                                           |
| Friendly name | string          | No       | An optional recognizable name for this alert contact.                                                                                                                                                                             |

#### Outputs

| Field            | Type    | Description                                              |
| ---------------- | ------- | -------------------------------------------------------- |
| Alert contact ID | string  | The exact identifier of the newly created alert contact. |
| Status           | integer | The contact's exact numeric activation status.           |
| Status name      | string  | A readable activation status label.                      |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/uptimerobot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
