In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
Choose this option if all alerts go to one channel. It’s the simpler setup.View dedicated integration setup steps
View dedicated integration setup steps
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Choose Cloudflare integration and click Save to generate a card
- Open the generated integration card and copy the Push URL
Use a shared integration
Choose this option if you need to route alerts to different channels based on the alert payload.Configure Cloudflare
1
Create a webhook destination in Cloudflare
Where: Cloudflare dashboard › Alerts › Destinations › Webhooks › CreateIn the older dashboard, Alerts is called Notifications.
Select Save and Test to save.
2
Make a notification use the webhook in Cloudflare
Where: Cloudflare dashboard › AlertsCreate or edit the notification you want to connect, and select the webhook from the previous step as its destination. After configuring the Webhook channel, you can use it in notification policies.
3
Verify
Where: Cloudflare dashboard › Alerts › notification ⋯ menu › TestSave and Test and Test only prove that Cloudflare can reach the URL. A successful test does not mean Flashduty received a usable alert event, so do not treat it as proof the integration works. Wait for a real notification to fire, then go back to Flashduty: when the integration shows a Latest event time, the setup works.
Status and severity
Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the alert pipeline.Cloudflare notifications carry no recovery event, so alerts do not recover automatically; close them manually or enable auto-close on timeout on the channel. The Alert Key is the
policy_id (notification policy ID) in the payload, so repeated notifications of one policy merge into one alert; without a policy_id it is random and every notification is a new alert.