skyfleetCloudflare
Every Cloudflare health check that goes unhealthy gets an agent. Paste an API token and Skyfleet makes the alert.
Go to Integrations → Cloudflare, press Add, paste a Cloudflare API token and press Connect. Make a custom token under My Profile → API Tokens for one account, with Account · Notifications · Edit and Zone · Health Checks · Read. Skyfleet then makes the Cloudflare side and lists what it made:
A webhook destination that posts to Skyfleet. Your source's token is its secret, which Cloudflare sends in the
cf-webhook-auth header. Cloudflare's test message is accepted and ignored.
A notification policy. If the account has health checks, the policy covers all of them going unhealthy. If it has none, it uses Passive Origin Monitoring instead: Cloudflare alerts when it can't reach your origin, in every zone of the account. Add a health check later and add the source again to switch.
Deleting the source deletes the policy and the destination.
Each health check is one issue in your Inbox. It starts an agent when it goes unhealthy and does nothing when it recovers.
Give every agent the Cloudflare tools
Go to Integrations → MCP servers → Cloudflare → Connect, sign in with Cloudflare and share it with your teammates. Agents can then search and call the Cloudflare API: DNS, Workers, logs and the rest through your login, on top of whatever started them.