IT OPS

Real-Time Outage Webhook to SLA Claim Tracker

Receives status-page incident webhooks the moment a vendor declares an outage, logs the timestamped event to a running tracker in Google Sheets.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVendor posts incident webhookHTTP webhook
  • LogicClassify event and compute elapsed downtime
  • ActionAppend timestamped event to outage trackerGoogle DriveGoogle Drive
  • LogicCheck downtime against SLA budget
  • OutputPost Slack alert when budget low or breachedSlack

What it does

Captures vendor incident notifications in real time instead of waiting for a monthly scrape. Each declared or resolved outage is logged with precise timestamps, and the workflow keeps a live tally of how much downtime budget remains before the vendor breaches its SLA.

When to use it

Use it when a vendor offers incident webhooks (Statuspage, Better Stack, custom) and you want an authoritative, timestamped record the moment downtime begins, plus an early-warning when you are close to a billable breach.

How it works

  1. 1An incoming webhook fires whenever the vendor posts an incident update.
  2. 2A logic step classifies the event as outage-start, update, or resolved and computes elapsed downtime.
  3. 3An action appends the timestamped event to the running outage tracker in Google Drive (a Sheet).
  4. 4A logic branch checks cumulative monthly downtime against the SLA budget.
  5. 5If the remaining budget is low or already breached, an output posts a Slack alert tagging the account owner with the current numbers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.