ActionUptimeRobotUpdated May 2026

How do I create an UptimeRobot monitor from a workflow?

Short answer: Drop the "UptimeRobot → Create Monitor" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 UptimeRobot actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Monitor Name friendly_name	string	Required	Monitor Name. e.g. "My Website"
URL url	url	Required	URL. e.g. "https://example.com"
Monitor Type type	options	Required	Monitor Type. Options: HTTP(s), Keyword, Ping, Port
Check Interval (seconds) interval	number	Optional	Min 60 for free, 30 for paid

Sample request

{
  "friendly_name": "My Website",
  "url": "https://example.com",
  "type": "{{trigger.type}}",
  "interval": "{{trigger.interval}}"
}

Returns

{
  "stat": "ok",
  "monitor": {
    "id": 456,
    "status": 1
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Monitor.

Any of these apps can fire this action as part of a workflow.

Google Sheets → UptimeRobot

2 Google Sheets triggers

HubSpot → UptimeRobot

18 HubSpot triggers

FAQ

Questions about Create Monitor.

What does the Create Monitor action do in UptimeRobot?

Creates a new UptimeRobot monitor (HTTP/HTTPS, keyword, ping, port) for the given URL and interval. Auto-provision monitors when a new service is deployed.

What inputs does Create Monitor require?

Required: Monitor Name, URL, Monitor Type. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if UptimeRobot returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Monitor support batch operations?

Yes. Run Create Monitor inside a Loop node to process arrays. Tiny Command handles UptimeRobot's rate limits automatically so you don't have to throttle manually.

More actions