Make monitor availability part of a regular review
Get a recurring availability summary for a monitor you identify, with returned uptime and incident details together in one report.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Monitor Availability
Tool to return an availability summary for a specific monitor. use when you need uptime percentage and incident details within an optional date range.
Why this helps
Remembering to review monitor availability can slip when it depends on a manual dashboard visit.
- Put a monitor availability review on a recurring schedule.
- Review returned uptime and incident details together.
- Reduce manual dashboard checks for a known monitor.
Setup
Build it in a few focused steps.
- 1Connect Notis to Better Stack once in the portal.
- 2Create a new automation in Automations, or tell Notis to create it from any channel.
- 3Describe the outcome: retrieve availability for the specified monitor ID and summarize returned uptime and incident details for the requested period.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real example using a valid monitor ID.
Questions about this workflow
Can this run for every monitor?
The action retrieves availability for a specific monitor. To review multiple monitors, provide the monitor IDs and ask Notis to retrieve each one.
Can I set the review period?
The action supports an optional date range. State the intended period in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Better stack. A trigger fires from one place; an action lands in another.
2chat triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Tool to create a new escalation policy. use when defining how incidents should escalate across team members.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Heartbeat Group
Tool to create a new heartbeat group. use when you need to organize related heartbeat checks under a single, logical group. example prompt: "create a new heartbeat group named 'backend services'."
Create Outgoing Webhook Integration
Tool to create a new outgoing webhook integration. use when you need to register an endpoint to receive event notifications from better stack.
Create Source Group
Tool to create a new source group. use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
Delete Escalation Policy
Tool to delete an escalation policy by id. use when you need to permanently remove an existing escalation policy after confirming its id.
Delete Source Group
Tool to delete a source group by id. use when you need to permanently remove an existing source group after confirming it is no longer needed.
Get Heartbeat
Tool to get a single heartbeat by id. use when you need to fetch details of a specific heartbeat.
Get Heartbeat Availability
Tool to retrieve availability summary for a specific heartbeat. use when you need availability metrics for a heartbeat within an optional date range.
Connect any two apps with Notis in the middle.
2chat and Better stack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Better stack.