Short answer: Drop the "UptimeRobot → Create Monitor" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"friendly_name": "My Website","url": "https://example.com","type": "{{trigger.type}}","interval": "{{trigger.interval}}"}
{"stat": "ok","monitor": {"id": 456,"status": 1}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.