Better Stack Automation, Incident Management & Approvals
Run Better Stack on autopilot. Keep the veto.
117 actions
Better Stack status pages, heartbeats, and escalation policies run inside your workflows. Rills queues the writes and deletes for approval before they execute.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential monitoring action from Better Stack arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue (3)
Post 2 status updates for incident #242?
API latency spike
5 services affected
38 min ago
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Clear runs stop waiting on you.
Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.
About Better Stack automation
Better Stack fires alerts and status updates the moment something breaks. But the same automation that posts a degraded performance notice can also publish a premature all-clear or update the wrong service page while you're still investigating.
When Better Stack runs unsupervised
Better Stack automation keeps your status page current, but it can also ship mistakes you catch only after customers see them.
- Create Status Update posts a resolution note before the incident is actually resolved, misleading customers.
- Update Status Page Resource changes the status of a component to 'Operational' while the outage is still spreading.
- Delete Severity removes a severity level, breaking alert routing for the next incident.
- Update Escalation Policy reassigns on-call rotations without verifying the new schedule, leaving alerts unacknowledged.
- Delete Urgency Group wipes a grouping that downstream automations depend on, causing silent failures.
What Rills does inside Better Stack
Rills watches for changes you'd want to review: status updates about to post, escalation policies about to shift, resources set to change on your status page. It proposes the action, surfaces the context, and waits for your approval.
The update still goes out; you just see it before your customers do.
Why Better Stack has no triggers and how Rills fills the gap
For teams that rely on Better Stack as a core productivity tool, the absence of native triggers means every status update and policy change happens without a human in the loop. Rills polls your Better Stack data on a schedule, checks for the patterns you care about, and brings proposed actions to your phone before they reach your status page.
- Poll for new incidents every 5 minutes, then propose a status update if one hasn't been sent yet.
- Check escalation policy assignments daily; if the on-call rotation has changed, propose an update to the policy.
- Scan status page resources hourly; if a component shows 'Major Outage' for too long, propose a verification update.
- At the end of each business day, review heartbeat groups for any that have gone silent, then propose a notification to the team.
What Rills can do in Better Stack
6 of 117 actions across reads, writes, and updates.
- 01
Acknowledge Incident
Tool to acknowledge an ongoing incident.
- 02
Create Escalation Policy
Creates an escalation policy that defines the sequence of notifications and actions when an incident occurs, ensuring the right people are notified in the correct order based on severity, schedule, or incident metadata.
- 03
Create Escalation Policy Group
Tool to create a new escalation policy group.
- 04
Create Heartbeat
Tool to create a new heartbeat monitor for cron jobs and scheduled tasks.
- 05
Create Heartbeat Group
Tool to create a new heartbeat group.
- 06
Create Incident
Tool to create a new incident and alert the on-call person.
Common questions about Better Stack automation
How do I automate Better Stack incident updates without losing control?
Rills proposes the incident update, you swipe to approve from your phone. Better Stack doesn't fire events directly to Rills, but you can set up triggers from monitoring tools, Slack, or a simple schedule. The action draft waits in your mobile queue. You decide what ships before it hits your status page. No dashboard babysitting.
Can I get mobile approvals before Better Stack status page changes go live?
When a monitor fires, Rills can draft a status update or a new resource. You get a notification on your phone. Swipe to approve the copy before it goes live. That way the status page never posts 'Investigating' when it should say 'Monitoring' because you caught the nuance.
How do I automate Better Stack status page resource creation safely?
Rills can propose a status page resource creation or an update based on context you provide (Slack messages, incident titles, monitor data). You review the draft on your phone and approve it. The resource isn't published until you say yes. No more wishing you'd double-checked the wording before it shipped.
Can I automate Better Stack severity changes while keeping a human in the loop?
Rills can suggest a severity change when an incident escalates. You see the proposed new severity and the reason on your phone. One tap to approve before it affects your notification rules. If the AI proposes a jump from minor to critical without justification, you veto it. No unattended priority shifts.
How is Rills different from Zapier for Better Stack automation?
Zapier executes actions automatically once you set rules. Rills adds a human approval layer. For Better Stack, that means a status update or severity change never lands on your public page until you've reviewed it. Approvals and logic are free; you only pay for real actions. You keep the veto.
Why use Rills instead of Make for Better Stack?
Make runs workflows without a pause for review. Rills inserts a mobile approval step before any customer-visible change. Your Better Stack status page, severity, or escalation policy only updates after you swipe. You get the leverage of automation without the risk of an unsupervised AI misstep.
Does Rills support Better Stack webhooks to trigger actions?
Rills can act on Better Stack via its API, but there are no built-in Better Stack webhook triggers. You can connect other signals (monitoring alerts, Slack commands, or a recurring schedule) to prompt Rills to propose status page actions. The proposal lands in your approval queue, not live on the page.
How much does Rills cost for Better Stack automation?
All approvals and workflow logic are free. You only pay when Rills performs a real action: an AI call that drafts a status update, or an API call that actually creates/updates a resource in Better Stack. No per-workflow fees, no seat licenses. You pay for the work that gets done, not the guardrails.