# Monitor Cloudflare incidents and alert with Slack and Telegram: n8n workflow

> Started by a clock, and works across Google Sheets, Jira, Slack and Telegram. It hands the judgement calls to OpenAI.

Source: https://millionrounds.com/workflow/monitor-cloudflare-incidents-and-alert-with-slack-and-telegr (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Alerts and monitoring](https://millionrounds.com/workflows?category=Alerts+and+monitoring#library)

# Monitor Cloudflare incidents and alert with Slack and Telegram

Started by a clock, and works across Google Sheets, Jira, Slack and Telegram. It hands the judgement calls to OpenAI. 25 steps, 4 branches: large, and worth reading before you trust it with anything live.

Large Calls a model: OpenAI

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fmonitor-cloudflare-incidents-and-alert-with-slack-and-telegr)

**25 steps** Large: read it before trusting it with anything live

**4** Branches: places the flow splits

**0** Loops or waits

**4** Services it connects to

## The flow

Starts it 1 Model 5 Logic 11 Service 8

The steps in the order they run, from what starts it.

- 1 **Schedule Trigger** Schedule trigger *Starts it*
- 2 **OpenAI Chat Model** Lm Chat Open Ai *Model*
- 3 **Structured Output Parser** Output Parser Structured *Model*
- 4 **OpenAI Chat Model1** Lm Chat Open Ai *Model*
- 5 **Decodo HTTP Request** Decodo *Service*
- 6 **CloudFlare OK?** If *Logic*
- 7 **CloudFlare Alert Bot** Agent *Model*
- 8 **Support Request Reader Agent** Agent *Model*
- 9 **Is top of hour?** If *Logic*
- 10 **Enrich Incidents & Score** Code *Logic*
- 11 **Alert team via Telegram** Telegram *Service*
- 12 **Send message via Slack1** Slack *Service*
- 13 **Submit JIRA request ticket** Jira *Service*
- 14 **Send message via Telegram** Telegram *Service*
- 15 **Send message via Slack** Slack *Service*
- 16 **No Operation, do nothing** No Op *Logic*
- 17 **Log Incidents** Google Sheets *Service*
- 18 **UTIL: Filter Already Alerted** Code *Logic*
- 19 **Setup Jira, Slack, Email** Set *Logic*
- 20 **UTIL: Prepare Notification Payload** Code *Logic*
- 21 **High Impact Escalation?** If *Logic*
- 22 **Send message to IT Support team** Slack *Service*
- 23 **Should broadcast notifications?** If *Logic*
- 24 **Low Impact Buffer** No Op *Logic*
- 25 **Skip Notification Broadcast** No Op *Logic*

## How it's built

- **Starts on:** A clock
- **Steps:** 25, with 4 branches
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Google Sheets, Jira, Slack, Telegram
- **Model:** OpenAI

## Questions

What does it need to run?

An n8n account, plus your own Google Sheets, Jira, Slack and Telegram accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 25 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 25 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fmonitor-cloudflare-incidents-and-alert-with-slack-and-telegr)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Google Sheets](https://millionrounds.com/workflows?service=Google+Sheets#library)[Jira](https://millionrounds.com/workflows?service=Jira#library)[Slack](https://millionrounds.com/workflows?service=Slack#library)[Telegram](https://millionrounds.com/workflows?service=Telegram#library)

## Workflows like it

Also alerts and monitoring, with the same services where possible, closest in size first.

- [**Monitor Clutch categories for new agencies with BrowserAct** 25 steps · calls a model · Google Sheets, Slack](https://millionrounds.com/workflow/monitor-clutch-categories-for-new-agencies-with-browseract)
- [**Monitor HTTP endpoints and send state-change alerts** 25 steps · Google Sheets, Slack](https://millionrounds.com/workflow/monitor-http-endpoints-and-send-state-change-alerts)
- [**Track inventory levels with Gmail and Slack** 25 steps · Gmail, Slack](https://millionrounds.com/workflow/track-inventory-levels-with-gmail-and-slack)
- [**Ad monitoring tool with Gemini** 24 steps · calls a model · Google Drive, Google Sheets](https://millionrounds.com/workflow/ad-monitoring-tool-with-gemini)
- [**Analyze Google Ads search terms with Claude and DeepSeek** 24 steps · calls a model · Discord, Slack](https://millionrounds.com/workflow/analyze-google-ads-search-terms-with-claude-and-deepseek)
- [**Analyze customer feedback and alert negative sentiment** 26 steps · calls a model · Gmail, Google Sheets](https://millionrounds.com/workflow/analyze-customer-feedback-and-alert-negative-sentiment)