IT OPS

Cloudflare health check failure to status draft

On a Cloudflare health-check failure, this confirms the outage is sustained, drafts a degraded-performance notice, and routes it to Microsoft Teams for sign-off before publishing.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCloudflare health check failsCloudflareCloudflare
  • LogicConfirm failure is sustained
  • ActionDraft degradation noticeOpenAI
  • ActionSend approval card to TeamsMicrosoft Teams
  • OutputPublish notice to status pageHTTP webhook

What it does

It watches Cloudflare health-check notifications and, once a failure is confirmed as sustained rather than a single blip, drafts a measured "degraded performance" status notice and sends it to Microsoft Teams for approval. Approved copy is published to the public status page.

When to use it

Use it when Cloudflare sits in front of your edge and you want a calm, accurate degradation notice that does not over-alarm customers over a transient flap. The sustained-failure gate keeps you from posting noise.

How it works

  1. 1Cloudflare sends a health-check notification webhook on a failing origin or pool.
  2. 2A logic step checks the failure has persisted past the configured threshold; transient single failures stop here.
  3. 3An OpenAI step drafts a partial-degradation notice naming the affected region or service in a steady tone.
  4. 4The draft goes to a Microsoft Teams approval card.
  5. 5On sign-off, the notice publishes to the status page via HTTP webhook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Connect HTTP webhookTrigger any URL on agent actions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.