Webhook logo
UptimeRobot logo

Workflow template

Create a UptimeRobot monitor from a webhook

Create an HTTP monitor in UptimeRobot from webhook JSON containing friendlyName, url, interval and timeout. Each accepted request creates a monitor in your writable account and uses an available monitor slot.

How it works

From a monitor request to a new HTTP monitor

1 Trigger · 1 Action
Webhook1 · Trigger

Monitor request

Receive friendlyName, url, interval and timeout as separate top-level fields. These values map to the new monitor, so restrict the webhook to senders authorized to create monitors in your account.

UptimeRobot2 · Action

Create monitor

Create an HTTP monitor with the four requested values. The prepared type is fixed to HTTP and assignedAlertContacts is an empty list; incoming fields do not override those constants.

The result

A new HTTP monitor using the supplied settings

Example UptimeRobot monitor webhook JSON

{ "friendlyName": "Example website", "url": "https://example.com", "type": "HTTP", "interval": 300, "timeout": 30, "assignedAlertContacts": [] }

Included fictional monitor request. interval and timeout are seconds. The action fixes HTTP type and an empty alert-contact list independently of the same fields shown in the sample.

Before activation

Set up your workflow

  1. Connect a writable UptimeRobot account

    Use an account permitted to create monitors and check that it has an available slot. This is a create operation rather than a status lookup.

  2. Prepare the four top-level input fields

    Send friendlyName, url, interval and timeout separately in webhook JSON. Review the HTTP type and empty assignedAlertContacts constants; edit those action settings deliberately if your monitoring policy needs contacts.

  3. Create one controlled test monitor

    Protect the webhook, activate and send one controlled request for a URL you are permitted to monitor. Inspect the resulting monitor and its settings in UptimeRobot before resending an uncertain request.

Details and limitations
  • Each request consumes a monitor slot. The recipe creates a monitor rather than finding or updating one by name or URL. Repeated requests and manual reruns can create additional monitors and consume more slots.

  • Monitor type and alert contacts are fixed. The action sets type to HTTP and assignedAlertContacts to an empty list. Incoming type or contact fields do not override those constants; no alert contacts are assigned by this starter.

  • Creation does not prove the monitored URL is healthy. Inspect the created monitor and its later checks in UptimeRobot. The workflow does not wait for an UP result, log future status changes to a spreadsheet or delete the monitor afterward.

Questions about this template

Which fields must my request supply?

Send friendlyName, url, interval and timeout at the top level. interval and timeout are in seconds, and each field is mapped separately to the HTTP monitor action.

Can the request choose the type or alert contacts?

Not with the prepared mappings. type is fixed to HTTP and assignedAlertContacts is fixed to an empty list. Change the action settings deliberately if you need a different contact configuration.

Will a repeated URL update the existing monitor?

No. Each accepted request creates a monitor and uses an account slot. No lookup or deduplication by name or URL is prepared, so reruns can create additional monitors.

Does a successful action mean the website is UP?

No. It means the monitor was created. Review its checks in UptimeRobot separately; the template does not wait for a health result or collect later status transitions.

Explore connected apps

App integrations