Cloudflare Notifications
Send Cloudflare notifications to an appkeepr channel with one generic webhook destination shared by your notification policies.
Setup
Create the connection
In appkeepr, open Sources → Integrations. Create a Cloudflare connection, choose a channel and optional project, then click Create connection. appkeepr generates a Webhook URL and Secret for this connection.
Create a webhook destination
In Cloudflare, open Notifications → Destinations and create a webhook. Enter a name, paste the Webhook URL into URL, and copy the appkeepr Secret into Secret. Select Save and Test.
Cloudflare sends this Secret in the cf-webhook-auth header. appkeepr requires it on incoming requests.
Connect your notification policies
Create or edit a Cloudflare notification policy and select this webhook as a delivery destination. The same destination can serve several policies, including different notification types.
Cloudflare owns the event selection and available notification types. appkeepr forwards the received notification text and available context through this connection's channel.
Manage the Secret
Opening Setup & status lets a workspace owner or admin copy the saved Secret again. Editing the connection's name, channel or project preserves it.
To rotate it, use Change Secret in appkeepr and configure the same replacement in the Cloudflare webhook destination. Cloudflare's API can update a webhook destination, including its Secret. If you create a replacement destination, select it in every policy that used the old one. Requests carrying the previous Secret will be rejected after the replacement is saved in appkeepr.
Verify delivery
Cloudflare's Save and Test success confirms that the webhook URL and Secret work. Its standard setup test does not create an Inbox message or send push.
To verify message publication, select this destination in a notification policy and send a notification through that policy. appkeepr accepts native notification text, including notifications without policy or alert-type metadata. A notification's name containing “Test” does not make it a setup test.
Notifications are stored in Inbox before webhook acknowledgement. OS push follows the channel subscription and device settings; successful webhook acceptance does not guarantee a phone notification.