Publish affiliate service outage reports from incoming alerts
When an affiliate service outage notification arrives, create a Better Stack status report with the information provided in the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Status Page Report
Creates a status page report for an incident or scheduled maintenance.
Why this helps
During an outage, status updates can lag while you switch from investigating the problem to writing a clear report.
- Turn an incoming outage notice into a status page report.
- Keep stakeholder communication moving during an incident.
- Reuse supplied incident details when drafting the report.
Setup
Build it in a few focused steps.
- 1Connect Adtraction and Better Stack once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create one from any channel.
- 3Describe that an affiliate service outage notification should create a Better Stack status page report using supplied details.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real outage notification and the relevant status page information.
Questions about this workflow
Will this workflow choose the right status page and report details automatically?
The request or your prompt must provide enough context to identify the intended status page and report. The workflow cannot infer missing identifiers or outage details.
Does Adtraction have a listed outage trigger?
No. This workflow starts with a Notis webhook request, which must be sent by an external system or process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adtraction to Better stack. A trigger fires from one place; an action lands in another.
Adtraction 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.
Adtraction 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.