Keep recurring campaign runs accountable
Create a heartbeat for a scheduled campaign process, then have the process check in regularly so missed runs are visible.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Heartbeat
Creates a heartbeat monitor that checks for regular signals from a service.
Why this helps
Recurring campaigns can be easy to forget when a scheduled process silently stops running.
- Create a Better Stack heartbeat for an identified recurring campaign task.
- Make missed check-ins easier to spot through Better Stack monitoring.
- Set up monitoring when the campaign schedule or process is ready.
Setup
Build it in a few focused steps.
- 1Connect AimTell and Better Stack once in the Notis portal.
- 2Create an automation in Automations, New Automation, and describe the outcome in one instruction.
- 3Tell Notis to create a Better Stack heartbeat for the recurring campaign process described in the request.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real scheduled process and confirm the heartbeat was created.
Questions about this workflow
Does creating the heartbeat automatically send check-ins?
No. The action creates a heartbeat monitor for a cron job or scheduled task. The monitored process still needs to send regular heartbeat signals.
Can AimTell start this automation when a campaign is scheduled?
No AimTell trigger events are available. Start it with a Notis webhook request when you are ready to set up monitoring.
What details should I provide?
Identify the recurring campaign process and provide the cadence or monitoring expectations needed to configure the heartbeat. Confirm any required details in Better Stack when testing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AimTell to Better stack. A trigger fires from one place; an action lands in another.
AimTell 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.
AimTell 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.