ActionBetter StackUpdated June 2026

How do I add a Better Stack uptime monitor?

Short answer: You can create uptime monitor in Better Stack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Better Stack Create Uptime 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.

Create Uptime Monitor in Better Stack — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
URL
url
stringRequiredA fully qualified URL (https://...) for the url.
Type
monitor_type
optionsOptional
Check Frequency (seconds)
check_frequency
stringOptional
Display Name
pronounceable_name
stringOptional
Sample request
{
"url": "e.g. https://example.com/path",
"monitor_type": "{{trigger.monitor_type}}",
"check_frequency": "{{trigger.check_frequency}}",
"pronounceable_name": "{{trigger.pronounceable_name}}"
}
Returns
{
"data": {
"id": "123",
"attributes": {
"url": "https://example.com",
"status": "up"
}
}
}

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

Triggered by

Apps that pair well as the trigger for Create Uptime Monitor.

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

FAQ

Questions about Create Uptime Monitor.

What does the Create Uptime Monitor action do in Better Stack?
Programmatically adds a new uptime check with URL, method, expected status code, request interval. The standard hook for "Vercel deployment finished → auto-add monitor for the new deployment URL" workflows.
What inputs does Create Uptime Monitor require?
Required: URL. 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 Better Stack 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 Uptime Monitor support batch operations?
Yes. Run Create Uptime Monitor inside a Loop node to process arrays. TinyCommand handles Better Stack's rate limits automatically so you don't have to throttle manually.
More actions

Other Better Stack actions.

Action
List Incidents
Returns active and historical incidents with filters by status and time range. For "what's currently firing" dashboards or "weekly incident report" rollups to the team.
Action
List Monitors
Returns every monitor in the team with current status, uptime percentage over a configured window, last-failure timestamp. Useful for "show me all monitors that have been flaky this month" maintenance workflows.
Create Uptime Monitor in Better Stack — start free