ActionUptimeRobotUpdated September 2026
How do I create an UptimeRobot monitor from a workflow?
Short answer: You can create monitor in UptimeRobot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the UptimeRobot Create Monitor action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
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 run history shows the failed step with its input and the error message UptimeRobot returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Monitor support batch operations?
Run Create Monitor inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within UptimeRobot's rate limits.
More actions