Turn Agility publish outages into actionable Better Stack incidents
A failed content release can wait for nobody. Send the publish error to Better Stack so the on-call team can start investigating with the relevant context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Why this helps
A publish failure can sit unnoticed while someone checks CMS logs and separately decides whether it warrants an incident.
- Route a confirmed publish outage into the incident process.
- Include the affected item and error details supplied by the webhook.
- Reduce the time spent relaying a release problem by hand.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and Better Stack once in the Notis portal.
- 2Create an automation named for Agility publish outages.
- 3Tell Notis to create a Better Stack incident when a webhook reports a publish failure caused by a service outage, including supplied item and error details.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real publish failure webhook and confirm the incident context.
Questions about this workflow
Does Agility CMS provide a native trigger for this workflow?
No. Start it with a Notis webhook. Send an HTTP request to the automation when your process detects the publish failure.
Can this determine whether every publish error is an outage?
Only if the webhook or your instruction supplies enough error context to identify an outage. Notis cannot infer unavailable information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Better stack. A trigger fires from one place; an action lands in another.
Agility cms 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.
Agility cms 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.