Check response history when someone reports slowness
Pair a report of a slow experience with monitoring history so you can decide what needs attention next.
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 fetch historical response times for specified monitors. use when you need performance trends over time after retrieving monitor ids.
Why this helps
A vague performance report can trigger a scramble across tools to find supporting evidence.
- Attach response history lookup to a specific report.
- Reduce tool switching during initial investigation.
- Give follow-up a clearer starting point.
Setup
Build it in a few focused steps.
- 1Connect Heartbeat and UptimeRobot to Notis once.
- 2Create an automation using an incoming webhook trigger in the portal or ask Notis conversationally.
- 3Use one instruction asking Notis to identify the affected monitor from the report and retrieve its response time history.
- 4Choose the report channel and have the source forward slow-site reports to the webhook.
- 5Test with a real report and confirm the relevant monitor is selected.
Questions about this workflow
Will the history prove what caused the slowdown?
No. It provides response time information to support investigation; it does not identify root cause by itself.
Can the report come from Heartbeat?
A custom backend or external sender can forward Heartbeat context to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Heartbeat to Uptimerobot. A trigger fires from one place; an action lands in another.
Heartbeat triggers
Uptimerobot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Monitor
Tool to create a new monitor. use when you need to start monitoring a url or service; call after obtaining a valid api key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Monitor
Tool to delete a monitor. use when you need to remove an existing monitor by its id; use after confirming the monitor id.
Edit Maintenance Window
Tool to edit an existing maintenance window. use when you need to update its name, timing, recurrence, or duration after confirming the window id.
Edit Monitor
Tool to edit an existing monitor. use after confirming the monitor id exists.
Edit Public Status Page
Tool to edit an existing public status page. use after confirming the page id. updates friendly name, monitor set, domain, and status options in one call.
Get Account Details
Tool to retrieve account details. use after authenticating with a valid api key to fetch account metrics.
Get Maintenance Windows
Tool to retrieve maintenance windows. use after confirming a valid api key.
Get Monitor Authentication Type
Tool to get authentication type for specified monitors. use after providing monitor ids to check http basic auth status.
Connect any two apps with Notis in the middle.
Heartbeat and Uptimerobot, 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 Uptimerobot.