Short answer: Drop the "Better Stack → Create Uptime 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 |
|---|---|---|---|
URL url | string | Required | A fully qualified URL (https://...) for the url. |
Type monitor_type | options | Optional | — |
Check Frequency (seconds) check_frequency | string | Optional | — |
Display Name pronounceable_name | string | Optional | — |
{"url": "e.g. https://example.com/path","monitor_type": "{{trigger.monitor_type}}","check_frequency": "{{trigger.check_frequency}}","pronounceable_name": "{{trigger.pronounceable_name}}"}
{"data": {"id": "123","attributes": {"url": "https://example.com","status": "up"}}}
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.