Turn campaign destination outages into incidents
When a campaign destination is confirmed down, bring the issue into your incident workflow with a Better Stack incident and on-call alert.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Why this helps
A broken campaign destination can sit in a dashboard or report until someone notices and raises it for the team.
- Create an incident when supplied status information confirms a destination outage.
- Route the issue through Better Stack's incident and escalation process.
- Keep scheduled checks focused on an actionable decision instead of repeated manual review.
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 review the campaign destination status information you supply and create a Better Stack incident only for a confirmed outage.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real outage example and confirm the incident appears in Better Stack.
Questions about this workflow
Can Notis read AimTell campaign delivery status on its own?
No AimTell trigger events are available here. Provide the relevant status information to Notis or make it available to the scheduled automation before asking it to decide whether to create an incident.
Will the incident notify the on-call person?
The Better Stack Create Incident action is described as creating an incident and alerting the on-call person, routed by the specified escalation policy or default team settings.
What schedule should I use?
Choose a cadence appropriate to how quickly you need to detect and respond to destination outages. The automation can only assess information available when it runs.
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.