Better Stack
Better Stack uptime monitors and incidents
Better Stack (formerly Better Uptime + Logtail) is the unified observability platform — uptime monitoring, log management, status pages, on-call alerting — built for modern engineering teams that want fewer tool boundaries. Tiny Command exposes three actions, no triggers (Better Stack alerts route through configured notification channels — Slack, Webhooks, PagerDuty, etc.; configure a Webhook channel pointing at a Tiny Command webhook trigger URL for "react to firing alert" workflows): List Monitors (every uptime monitor in the team), List Incidents (active and historical incidents with filters), Create Monitor (add a new uptime check with URL, method, expected status code, request interval). The connection uses a Better Stack API token from team settings. The Create Monitor pattern is the workflow shape for "auto-add monitoring when we deploy a new service" — a Vercel deployment trigger fires a workflow that Creates a Monitor against the new deployment URL with the right alert routing pre-configured. Better Stack's monitor checks come from regions globally (configurable per monitor); the default of 3-region consensus avoids single-region false-positives.
Do anything Better Stack can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Uptime Monitor | 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. |
| 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. |
| 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. |
Pre-built Better Stack workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Better Stack event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Better Stack into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Better Stack once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Better Stack field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Better Stack integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Better Stack to Tiny Command?
What Better Stack triggers does Tiny Command support?
What Better Stack actions can I run from a workflow?
Is the Better Stack integration real-time?
Do I need to write code to use Better Stack with Tiny Command?
How much does the Better Stack integration cost?
More other apps people connect.
Same category as Better Stack, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Better Stack.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
