Check monitor response times after a performance alert
Get the performance context you need while the signal is still fresh.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Monitor Response Times
Tool to return response times for a specific monitor. use when you have a monitor id and need performance metrics over the last 24 hours.
Why this helps
Teams lose time switching between alert payloads and performance dashboards during investigations.
- Start analysis from an existing alert pipeline
- See recent response time behavior quickly
- Give responders a concise investigation brief
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and Better Stack in Notis once.
- 2Create an automation named Incident response time check.
- 3Tell Notis to use the webhook context to identify the relevant monitor and retrieve its response times for the last 24 hours.
- 4Choose the webhook trigger and report channel.
- 5Send one real alert payload to test the workflow.
Questions about this workflow
What must the webhook include?
It should provide enough context to identify the relevant Better Stack monitor, such as a monitor id or clear monitor reference.
Does this change monitor settings?
No. It only retrieves response time data and summarizes it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 0CodeKit to Better stack. A trigger fires from one place; an action lands in another.
0CodeKit 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.
0CodeKit 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.