Skip to content
Notis

Check monitor status when an incident is raised

Bring a Heartbeat incident request into Notis and get the matching service status without a separate manual lookup.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Get Monitors

Tool to fetch monitor details and status. use after confirming account connection.

Why this helps

During an incident, switching between community discussion and monitoring tools makes it harder to stay focused.

  • Turn an incoming incident request into a monitor lookup.
  • Keep incident triage focused on the relevant status.
  • Reduce manual back-and-forth between tools.

Setup

Build it in a few focused steps.

  • 1Connect Heartbeat and UptimeRobot to Notis once.
  • 2Create an automation in the portal and choose an incoming webhook, or ask Notis to create it conversationally.
  • 3Write one plain-language instruction to use the incoming incident context to identify relevant monitors and retrieve their status.
  • 4Choose the channel for run reports and configure the external sender to call the generated webhook.
  • 5Test with a real incident request and verify the reported monitors.

Questions about this workflow

Does Heartbeat trigger this directly?

No. Notis receives an incoming webhook; a custom sender can forward the relevant Heartbeat incident context.

Will this resolve the incident?

No. It retrieves monitor status to support the follow-up.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

Edit Monitor

Tool to edit an existing monitor. use after confirming the monitor id exists.

ActionInstant

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.

ActionInstant

Get Account Details

Tool to retrieve account details. use after authenticating with a valid api key to fetch account metrics.

ActionInstant

Get Maintenance Windows

Tool to retrieve maintenance windows. use after confirming a valid api key.

ActionInstant

Get Monitor Authentication Type

Tool to get authentication type for specified monitors. use after providing monitor ids to check http basic auth status.

ActionInstant

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.