A New Look at the Notification Platform
Cloudflare’s Notification center has evolved since its 2019 debut as a centralized hub for account-level alerts. While much of the conversation has focused on the growing list of notification types, the underlying platform has seen significant updates that change how — and how reliably — customers receive critical alerts.
Notifications sit at the heart of Cloudflare’s value proposition: when your Internet property is under attack or experiencing errors, you need to know immediately. The alternative is manually refreshing analytics pages. Cloudflare offers notifications for events like DDoS attacks, unusual spikes in Firewall blocks, elevated 5xx errors from your origin, and above-average CPU usage in Workers scripts. New notification types are added regularly, with the full list maintained in Cloudflare Development Docs.
Why Webhooks Are Replacing Email
The classic delivery method — email — has an obvious weakness: it may never reach the person who needs to act. A notification buried in spam or an overcrowded inbox is effectively lost. For teams relying on Slack, Microsoft Teams, Discord, or other messaging platforms, waiting for email isn’t practical.
Webhooks solve this by delivering events directly to the services you already monitor. They follow a simple, standardized API pattern: one service sends an event to another. The destination can be a messaging platform, a data management system, a workflow automation tool, or your own internal API.
Cloudflare has long supported webhooks for Slack, Microsoft Teams, Google Chat, and custom APIs. Recently, support was added for DataDog, Discord, OpsGenie, and Splunk. Setup instructions for each type are available in the Cloudflare Development Docs. Adoption is accelerating rapidly: the number of configured webhooks doubles on average every three months. Webhooks are managed from the Notifications tab in the dashboard.
Notification History: A Safety Net for Missed Alerts
Even with webhooks, notifications were inherently ephemeral. Once sent, Cloudflare had no visibility into whether the alert was seen or recorded. If a notification was accidentally deleted, or a new teammate wasn’t added to the recipient list, the information was gone.
Notification history addresses this gap. Users can now access a log showing which notifications were sent, when they were sent, and to whom. Free, Professional, and Business plans retain history for the past 30 days; Enterprise plans retain it for 90 days.
At present, notification history is only accessible programmatically via the API. A dashboard view is planned for future releases.
