Cloudflare Incident Monitoring & Escalation Workflow

Who this workflow is for

For DevOps, SRE, IT Ops, and Platform teams running production traffic behind Cloudflare who need reliable incident awareness without alert fatigue.
Use it if you want:

• Continuous Cloudflare incident monitoring
• Clear severity-based routing
• Automatic escalation into JIRA
• Clean Slack & Telegram notifications
• Deduplicated, noise-controlled alerts

What this workflow does

This workflow polls the Cloudflare Status API, detects unresolved incidents, scores their impact, and routes them to the right channels.
High-impact incidents are escalated to JIRA.
Lower-impact updates are notified (or skipped) to reduce noise.

How it works (high level)

1. Runs on a fixed schedule (e.g. every 5 minutes)
2. Fetches current Cloudflare incidents
3. Stops early if no active issues exist
4. Normalizes and scores incidents (severity, impact, affected service)
5. Deduplicates previously-alerted incidents
6. Builds human-readable notification payloads
7. Routes by impact:
   • High → create JIRA incident + notify
   • Low → notify or suppress
8. Sends alerts to Slack and Telegram

Requirements

• n8n (self-hosted or Cloud)
• Cloudflare Status API (public)
• Slack bot (chat:write)
• Telegram bot + chat ID
• JIRA project with issue-create permission
• Optional LLM credentials (summarization/classification)

Notes

• All secrets are stored in n8n Credentials
• Workflow is idempotent and safe to rerun
• No assumptions about root cause or remediation
  Built for production-grade incident visibility with n8n.

Built with ❤️ using n8n