Skip to content

Webhooks for Notification Channels

A webhook sends each alert as one HTTPS request with a JSON body to an address you give. FlyWP builds the page for n8n, and it works with any receiver that accepts a JSON POST over HTTPS. See Send alerts to n8n for a full walkthrough.

Webhooks are available on paid plans, and only the team Owner and members with the Team Admin role can add, change, or remove them.

To add a webhook:

  1. Go to Team Settings → Notification Channels.

  2. In the Webhooks card, click Add webhook.

    Webhooks card on the Notification Channels page with the Add webhook button

  3. Fill in the details:

    FieldWhat to enter
    NameA name for the webhook, up to 50 characters.
    URLThe address that receives the alerts. It must start with https://.
    Auth header (optional)A header name and value FlyWP sends with every request. See Auth header.
  4. Click Send test to check the address. FlyWP shows Delivered with the answer code and time, or Failed with the reason.

    Add webhook form filled in, with the Failed result shown next to Send test

  5. Click Next, choose the alerts level and the servers, then click Save.

    Alerts step of the Add webhook window with Critical only selected and the Save button

After you save, the Webhooks card lists the webhook with its address (only the end of the path shows), its status and Last delivery. A team can have up to 5 webhooks, and one address can be added once.

Webhooks card with the saved Ops workflow webhook, its Connected and Header auth badges and the text No delivery yet

  • The address must use https:// and a public host name or IP address. FlyWP does not send to private or local addresses, or to FlyWP's own addresses.
  • FlyWP does not follow redirects. Use the final address.
  • The receiver has 10 seconds to answer.
  • The address can be up to 2,048 characters.

An auth header lets your receiver check that a request really comes from your FlyWP team. FlyWP sends the header you set on every request, including tests.

  • Header name: letters, digits and hyphens, up to 64 characters. Names that FlyWP or HTTP sets itself are not allowed, such as Content-Type, Host, User-Agent and anything that starts with X-FlyWP-.
  • Header value: printable characters on one line, up to 512. Click Generate to make a random 32-character value, and the copy button to copy it.
  • FlyWP stores the value encrypted and never shows it again.
  • The webhook row shows a Header auth badge when a header is set.

In the webhook row, open the menu and click Edit.

Webhook row menu with Send test, Pause, Edit, Delivery log, Alerts, Servers and Remove

  • Leave URL empty to keep the current address. The field shows the masked address as a hint.
  • Leave Header value empty to keep the stored value. Clear Header name to remove the header.
  • A new address can be tested with Send test before you save.
  • Use the Alerts and Servers menu items to change what the webhook gets, as for any channel.

FlyWP records a change of a webhook's address or auth header in the team activity log. The log holds the host name or the header name only, never the full address or the header value.

Send test sends a sample alert. You can use it in the add and edit forms before you save, and from the row menu of a connected webhook.

  • A test body has "test": true, the title Test alert from FlyWP and the event test.
  • Tests from the add and edit form are limited to 10 an hour for your team and 20 an hour for each person across all their teams. A test from a saved webhook's row menu uses the team limit of 10 an hour. After that, FlyWP says Test limit reached, try again later.
  • Slack and Telegram tests are limited to 3 a day for each channel.

Open the row menu and click Delivery log to see the last 50 deliveries from the last 30 days. Each one shows Delivered, Delivered after retries, Waiting, Failed or Not sent: resolved first, the time taken, the body FlyWP sent and the first 1 KB of the answer.

Delivery log window listing delivered, waiting and failed deliveries

To send a failed delivery again, open it and click Resend. The body and the id stay the same. You can resend 10 times an hour for each webhook and 10 times for each delivery. FlyWP does not resend an alert whose problem is already over, so your receiver never gets down after up.

A failed delivery opened in the Delivery log with the Resend button

What the receiver doesWhat FlyWP does
Answers with a 2xx codeMarks the delivery Delivered.
Answers 408, 429 or a 5xx code, does not answer in 10 seconds, or cannot be reachedTries again after 1, 5 and then 15 minutes. If the receiver answers 429 with a Retry-After number of seconds, FlyWP waits that long, up to 15 minutes.
Answers with a redirect or another 4xx codeFails the delivery at once. A retry would get the same answer.
Has an invalid certificateFails the delivery at once. Fix the certificate.

While FlyWP waits to retry, the row shows Failing with the reason. A delivery that fails after all retries counts as a failure. After 5 failed deliveries in a row, FlyWP pauses the webhook (Paused) and raises the Notification channel stopped alert. One delivered alert resets the count. Fix the problem, then click Resume on the row. A paused channel sends nothing, and FlyWP does not replay the alerts it missed.

You can also Pause and Resume a Slack or Telegram channel by hand from its row menu.

These are the alerts a channel can receive. The Event column is the code a webhook sends in the event field. For how alerts reach each person by email and in the app, see Notifications.

CategoryEventAlertSeverity
Serverssrv-01Server provisionedInfo
Serverssrv-02Server provisioning failedCritical
Serverssrv-03Server not reportingCritical
Serverssrv-04Server back onlineInfo
Serverssrv-05High CPUWarning
Serverssrv-06CPU back to normalInfo
Serverssrv-07High memoryWarning
Serverssrv-08Memory back to normalInfo
Serverssrv-09Low disk spaceWarning
Serverssrv-10Disk almost fullCritical
Serverssrv-11Disk space back to normalInfo
Serverssrv-12SSH key could not be added to a serverInfo
Serverscmp-12Memory limits for the apps of a serverWarning
Sitessit-01Site in a failed stateCritical
Sitessit-02Plugin or theme update failedWarning
Sitessit-04Bulk update finishedInfo, or Warning if anything failed
Sitessit-05Site still in maintenance modeWarning
Sitesmig-01Migration completedInfo
Sitesmig-02Migration failedWarning
Sitescmp-01Docker Compose Apps stopped on the Free planCritical
Sitescmp-02Docker Compose Apps will be removedCritical
Sitescmp-03Docker Compose service is downWarning
Sitescmp-04Docker Compose service runs againInfo
Sitescmp-05Docker Compose service keeps restartingWarning
Sitescmp-06Docker Compose service ran out of memoryWarning
Sitescmp-07Docker Compose health check failsWarning
Sitescmp-08Docker Compose App is downCritical
Sitescmp-09Docker Compose App runs againInfo
Sitescmp-11Docker Compose App stopped for a full diskCritical
Backupsbkp-01Backup failedWarning
Backupsbkp-02Backups pausedCritical
Backupsbkp-03No recent backupCritical
Backupsbkp-04Backup storage rejected your credentialsCritical
Backupsbkp-05Restore failedCritical
Securitysec-01Critical vulnerability foundCritical
Securitysec-03File integrity issues foundCritical
Securitysec-04Integrity check could not runWarning
Securitysec-05Vulnerability scan failedWarning
Securitysec-06SSH key added to a serverWarning
Deploymentsdep-01Deploy succeededInfo
Deploymentsdep-02Deploy failedWarning
Deploymentsdep-03Git connection lost, deploys stoppedCritical
Deploymentscmp-10Docker Compose deploy failedWarning, or Critical if the automatic rollback could not run
Domains & SSLssl-02SSL certificate expires in 3 daysCritical
Domains & SSLssl-03SSL certificate renewal failedCritical
Domains & SSLssl-04SSL certificate renewedInfo
Domains & SSLssl-05SSL certificate expiredCritical
Uptimeupt-01Site is downCritical
Uptimeupt-02Site is back upInfo
Billingbil-01Invoice availableInfo
Billingbil-02Payment failedCritical
Billingbil-03Final warning before suspensionCritical
Billingbil-04Payment successfulInfo
Billingbil-05Upcoming billingInfo
Teamtea-01Member joined the teamInfo
Teamtea-02Role changedWarning
Teamtea-03Notification channel stoppedWarning

Notes:

  • Uptime alerts need the Uptime Monitor add-on. The category only shows when your team has it.
  • Billing alerts can be routed by the team Owner only. Billing and Team alerts are about the team, so the server choice does not apply to them.
  • Account security messages (email change, passkey changes, FlyWP support sessions and similar) go only to the person they concern, by email and in the app. They never go to a channel.
  • When several sites fail at once, FlyWP can send one combined alert for Backup failed, Backup storage rejected your credentials and Critical vulnerability found. Webhooks get it in rolled_up.

Every request is a POST with Content-Type: application/json. Every key is always present, with null when it has no value.

KeyTypeWhat it is
versionnumberFormat version. Currently 1.
idstringThe delivery ID. It is the same on every retry and on Resend, so your receiver can drop a duplicate.
eventstringThe alert code, such as upt-01. See the alert codes. A test uses test.
event_labelstringThe name of the alert, such as Site is down.
severitystringcritical, warning or info.
titlestringThe headline.
detailsstringThe body text, as plain text. Paragraphs are separated by a blank line.
urlstring or nullA link to the item in FlyWP.
occurred_atstring or nullWhen it happened, in UTC (ISO 8601, ending in Z).
teamobjectid and name of your team.
serverobject or nullid and name of the server, when the alert is about a server or a site.
siteobject or nullid and domain of the site, when the alert is about a site.
recoverybooleantrue when the problem has ended.
duration_secondsnumber or nullOn a recovery, how long the problem lasted.
related_idstring or nullOn a recovery, the id of the alert it closes.
rolled_upobject or nullWhen one alert covers several sites: count and the list sites.
testbooleantrue for a test.

FlyWP may add keys in the future, so ignore keys you do not know.

An alert, here a site that goes down:

{
"version": 1,
"id": "48213",
"event": "upt-01",
"event_label": "Site is down",
"severity": "critical",
"title": "example.com is down",
"details": "example.com has stopped responding to FlyWP's uptime monitor.\n\n• Down since: 16 Nov 2026, 09:12 UTC\n\n• Last response: 16 Nov 2026, 09:11 UTC\n\n• Server: web-01\n\nIf other sites on web-01 are also down, the server itself is the place to start.",
"url": "https://app.flywp.com/site/1234/overview",
"occurred_at": "2026-11-16T09:12:40Z",
"team": { "id": 77, "name": "Acme Agency" },
"server": { "id": 310, "name": "web-01" },
"site": { "id": 1234, "domain": "example.com" },
"recovery": false,
"duration_seconds": null,
"related_id": null,
"rolled_up": null,
"test": false
}

The recovery arrives as a new request. It has its own id, "event": "upt-02", "recovery": true, the length of the outage in duration_seconds, and "related_id": "48213".

FlyWP also sends two headers with every request:

HeaderValue
X-FlyWP-EventThe same code as event.
X-FlyWP-DeliveryThe same value as id.

The User-Agent is FlyWP/1.0 (+https://flywp.com).

If you do not use n8n, check the auth header and drop duplicates. This Node.js example expects the header X-Auth-Token:

import express from 'express';
import { timingSafeEqual } from 'node:crypto';
const app = express();
const secret = Buffer.from(process.env.FLYWP_WEBHOOK_SECRET);
const seen = new Set(); // use a database or cache in production
app.post('/flywp-alerts', express.json(), (req, res) => {
const sent = Buffer.from(req.get('X-Auth-Token') ?? '');
if (sent.length !== secret.length || !timingSafeEqual(sent, secret)) {
return res.sendStatus(401);
}
const alert = req.body;
if (seen.has(alert.id)) {
return res.sendStatus(200); // a retry or a Resend: already handled
}
seen.add(alert.id);
if (!alert.test) {
console.log(`[${alert.severity}] ${alert.title}`);
}
res.sendStatus(200); // answer with a 2xx code within 10 seconds
});
app.listen(3000);

Answer with a 2xx code as soon as you have the alert. Do the slow work after you answer, because FlyWP waits 10 seconds and then tries again.

Still stuck? How can we help?

View as Markdown