Keep scheduled device publishing visible
Review the availability of a heartbeat that represents a scheduled Adafruit IO publishing job, and get a recurring run report without creating duplicate monitors.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Heartbeat Availability
Retrieves the availability summary for a heartbeat check.
Why this helps
Scheduled device publishing can quietly stop, and checking its heartbeat status by hand is easy to forget.
- Retrieves availability for the configured Better Stack heartbeat on a recurring schedule.
- Keeps a regular check of a scheduled publishing job in your run reports.
- Avoids repeatedly creating heartbeat resources.
Setup
Build it in a few focused steps.
- 1Connect Better Stack in Notis and create or identify a Better Stack heartbeat that represents the scheduled device publishing job.
- 2Create an automation in Notis and name it for the heartbeat availability review.
- 3Tell Notis to retrieve availability for that heartbeat and summarize the returned status in the run report.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with the configured heartbeat and confirm the returned availability details.
Questions about this workflow
Does this check Adafruit IO directly?
No. It retrieves availability for a Better Stack heartbeat. Your publishing process must already send heartbeat signals for the result to reflect its status.
Will the workflow create a heartbeat each time it runs?
No. It retrieves availability for the heartbeat you identify during setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Better stack. A trigger fires from one place; an action lands in another.
Adafruit IO triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Creates an incident escalation policy that defines who is notified and when.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Acknowledge Incident
Acknowledges an active incident, stopping further escalations.
Create Heartbeat Group
Creates a group to organize related heartbeat checks.
Create Outgoing Webhook Integration
Creates an integration to send event notifications to an endpoint.
Create Heartbeat
Creates a heartbeat monitor that checks for regular signals from a service.
Create Source Group
Creates a group to organize related log sources.
Delete Escalation Policy
Permanently deletes an escalation policy.
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Connect any two apps with Notis in the middle.
Adafruit IO 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.