Infrastructure
Cloudflare Webhooks
Web infrastructure platform. Receive events for security alerts, Workers deployments, and notification webhooks.
Connecting Cloudflare to Hookbase
Create a source in Hookbase first — it gives you an ingest URL to paste into Cloudflare. Then:
- 1Go to Cloudflare Dashboard → Notifications → Destinations
- 2Click "Create" under Webhooks and paste your Hookbase ingest URL
- 3Optionally add a shared secret as a URL parameter
- 4Create notification policies and select your webhook destination
Signature verification
Cloudflare does not sign its webhooks with an HMAC scheme, so a signing secret on the source would have nothing to verify. Use a custom source with no secret, and keep the ingest URL itself hard to guess.
How Cloudflare secures them instead: Cloudflare notification webhooks use a shared secret in the URL path. Use a unique Hookbase source slug.
Cloudflare event types
6 of the events people route most often. Hookbase accepts every event Cloudflare sends, whether or not it is listed here.
ssl.universal_certificate_renewal
A Universal SSL certificate was renewed
dns.record_changed
A DNS record was changed
firewall.block
A request was blocked by the firewall
workers.deployment
A Workers script was deployed
pages.deployment
A Pages project was deployed
health_check.status_changed
A health check status changed
What a Cloudflare webhook looks like
A health_check.status_changed payload. Hookbase stores the raw body exactly as it arrived, so this is also what you get back on a replay.
{
"text": "Health check status changed",
"data": {
"health_check_id": "hc-123456",
"health_check_name": "API Health",
"new_status": "Unhealthy",
"old_status": "Healthy",
"time": "2024-01-15T10:30:00Z",
"reason": "HTTP timeout after 10s"
}
}Start receiving Cloudflare webhooks
Create a source, paste the URL into Cloudflare, and watch the first event arrive. The free tier includes 1,000 events a month.
Get Started Free