# Create, update alerts UptimeRobot tool MCP server all 21: n8n workflow

> Started by an event in a connected app. It calls services over plain HTTP rather than through connectors.

Source: https://millionrounds.com/workflow/create-update-alerts-uptimerobot-tool-mcp-server-all-21 (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Setup and learning](https://millionrounds.com/workflows?category=Setup+and+learning#library)

# Create, update alerts UptimeRobot tool MCP server all 21

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 22 steps: large, and worth reading before you trust it with anything live.

Large

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-update-alerts-uptimerobot-tool-mcp-server-all-21)

**22 steps** Large: read it before trusting it with anything live

**0** Branches: places the flow splits

**0** Loops or waits

**0** Services by connector: it calls them over plain HTTP

## The flow

Starts it 1 Service 21

The steps in the order they run, from what starts it.

- 1 **Get an account** Uptime Robot Tool *Service*
- 2 **Create an alert contact** Uptime Robot Tool *Service*
- 3 **Delete an alert contact** Uptime Robot Tool *Service*
- 4 **Get an alert contact** Uptime Robot Tool *Service*
- 5 **Get many alert contacts** Uptime Robot Tool *Service*
- 6 **Update an alert contact** Uptime Robot Tool *Service*
- 7 **Create a maintenance window** Uptime Robot Tool *Service*
- 8 **Delete a maintenance window** Uptime Robot Tool *Service*
- 9 **Get a maintenance window** Uptime Robot Tool *Service*
- 10 **Get many maintenance windows** Uptime Robot Tool *Service*
- 11 **Update a maintenance window** Uptime Robot Tool *Service*
- 12 **Create a monitor** Uptime Robot Tool *Service*
- 13 **Delete a monitor** Uptime Robot Tool *Service*
- 14 **Get a monitor** Uptime Robot Tool *Service*
- 15 **Get many monitors** Uptime Robot Tool *Service*
- 16 **Reset a monitor** Uptime Robot Tool *Service*
- 17 **Update a monitor** Uptime Robot Tool *Service*
- 18 **Create a public status page** Uptime Robot Tool *Service*
- 19 **Delete a public status page** Uptime Robot Tool *Service*
- 20 **Get a public status page** Uptime Robot Tool *Service*
- 21 **Get many public status pages** Uptime Robot Tool *Service*
- 22 **UptimeRobot Tool MCP Server** Mcp trigger *Starts it*

## How it's built

- **Starts on:** An event in a connected app
- **Steps:** 22
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Nothing by connector; it calls services over plain HTTP
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 22 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 22 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-update-alerts-uptimerobot-tool-mcp-server-all-21)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Workflows like it

Also setup and learning, with the same services where possible, closest in size first.

- [**Close tickets faster Zammad tool MCP server all 20 operations** 22 steps](https://millionrounds.com/workflow/close-tickets-faster-zammad-tool-mcp-server-all-20-operation)
- [**Expose Google Blogger management tools to Claude with MCP** 22 steps](https://millionrounds.com/workflow/expose-google-blogger-management-tools-to-claude-with-mcp)
- [**Gmail MCP server – your all‑in‑one AI email toolkit** 22 steps · Gmail](https://millionrounds.com/workflow/gmail-mcp-server-your-all-in-one-ai-email-toolkit)
- [**INST - the n8n installer: deploy workflows with GitHub** 22 steps · GitHub](https://millionrounds.com/workflow/inst-the-n8n-installer-deploy-workflows-with-github)
- [**Build an MCP server with Google Calendar** 22 steps · calls a model · Google Calendar](https://millionrounds.com/workflow/build-an-mcp-server-with-google-calendar)
- [**Airtop tool MCP server all 20 operations** 21 steps](https://millionrounds.com/workflow/airtop-tool-mcp-server-all-20-operations)