Notifications & alerts
Route fleet alerts to email, Slack, and signed webhooks, and control exactly which events go where.
FleetWP sends alerts through multiple channels and lets you decide, per event type, which channels receive them. Everything is configured on the fleet Notifications page (admin only).
Channels
- Email — sent to your configured recipients; falls back to the workspace owner's email if no recipients are set.
- Slack — an incoming-webhook URL; alerts arrive as formatted message blocks.
- Webhook — a signed HTTP POST to your endpoint. Each request carries an
X-FleetWP-Signature: sha256=<hmac>header so you can verify authenticity with your webhook secret.
Slack and webhook deliveries go through an SSRF guard. Delivery is best-effort and isolated per channel — a failure in one never blocks the others or your monitoring.
Alert kinds
| Kind | Fires when | Source |
|---|---|---|
uptime | A site goes down or recovers | Uptime cron |
offline | The site is up but the agent is silent | Uptime cron |
security | A new high/critical hardening finding | Scan cron |
backup | A backup fails | Backup status callback |
errors | A new fatal/parse PHP error | Heartbeat |
links | New broken links found | Manual link scan |
edge | A Cloudflare threats spike | Edge cron |
Routing matrix
The Notifications page has a matrix of alert kind × channel. By default an alert goes to every channel that's configured — absence means on. Untick a cell to stop a specific kind from reaching a specific channel.
Testing
Each channel has a Send test button so you can confirm delivery end-to-end. You can also rotate the webhook signing secret from the same page.