- When an alert fires, someone has to stop and write the first update. This template drafts it from your playbook.
Workflow template · Operations

A clear first update for every incident
Responders and stakeholders get the same facts from one alert.


Received
Summarize incident alert
Notify incident channel
Email incident update
- Your monitoring tool sends each alert to the OAIZ API as an incident alert event.
- An LLM Call reads it with your playbook. It keeps what the alert shows apart from guesses, and suggests a first check.
- The summary goes to your incident channel in Slack, then Gmail sends a plain status update to your stakeholders.
An alert arrives
Summarized with your playbook
Responders and stakeholders informed
Received
Summarize incident alert
Notify incident channel
Email incident update
Starts onReceived
Event type incident-alerts/received, sent to the OAIZ API with an API key.
Knowledge document
Incident severity and escalation playbook
Observed impact, hypotheses and missing facts
A first investigation step
No invented cause or recovery time
#incidentsCheckout error rate above 5% since 14:02. Impact: failed card payments, as the alert reports. Cause: not confirmed. First check: checkout deploys in the last hour.
Incident status updateWe are investigating failed card payments at checkout. The cause is not yet confirmed.
- Before you go live, have your monitoring send alerts to OAIZ, and connect Slack and Gmail.
- Set the channel and the recipients, and replace the starter playbook with your own.
- Then test it with Run workflow, and choose Go live.
Before you go live
Send alerts to the OAIZ API
Connect Slack
Connect GmailSet the channel and recipients
Replace the playbook with yours
Run workflow
Not liveLiveGo live