Email Check: webhook alerts

An email alert cannot reach you when email is what broke. A webhook sends the alert over HTTP instead: when a check fails, Email Check posts a short message to a URL you choose, and the service behind that URL puts it in front of you.

The webhook is optional. With the field empty, the plugin makes no outside requests. The URL must be a public http or https address on port 80, 443 or 8080. WordPress refuses localhost, private network addresses and other ports, so a receiver on your own network, or one on a port such as 5678 (n8n’s default), needs a public address on one of those ports, usually behind a reverse proxy. If the URL is not valid, the plugin keeps the previous one and shows an error. A new URL starts fresh: it gets no recovery message for a failure that went to the old one.

What the plugin sends

One HTTP POST with a JSON body (Content-Type: application/json; charset=utf-8):

  • on every failed check, and
  • once on the first passing check after a failure, so you know it is fixed. If that message is not delivered, the next passing check sends it again.

Passing checks after that send nothing. The recovery message reads “Email check passed again on https://example.com.” When a check fails with no error text, the error field says so: “wp_mail() returned false and gave no error message.”

{
  "text": "Email check failed on https://example.com: SMTP Error: Could not authenticate.",
  "site": "https://example.com",
  "status": "fail",
  "error": "SMTP Error: Could not authenticate.",
  "time": "2026-11-18T09:00:00+00:00"
}
Field Value
text One readable line, for services that show a message as-is
site The site’s home URL
status fail, or pass on the recovery message
error The error text from the check; empty on the recovery message
time When the check ran, ISO 8601 in UTC

Treat the webhook URL as a password. Anyone who has it can post to your channel.

Slack

  1. Create a Slack app for your workspace, turn on Incoming Webhooks, and add a webhook to the channel you want.
  2. Copy the URL. It starts with https://hooks.slack.com/services/.
  3. Paste it into the Webhook URL field on the Email Check screen.

Slack shows the text line.

Google Chat

  1. In the Chat space, open Apps & integrations and add a webhook.
  2. Copy the URL. It starts with https://chat.googleapis.com/.
  3. Paste it into the Webhook URL field.

Google Chat rejects fields it does not know, so for a Google Chat URL the plugin sends only the text field.

Discord

Discord webhooks expect a different body, but each one also has a Slack-compatible address. Copy the webhook URL from the channel’s Integrations settings and add /slack to the end before you paste it.

Any other receiver

Automation services (Zapier, Make, n8n) offer a “catch webhook” trigger that accepts any JSON and can pass it on to SMS, Microsoft Teams, a ticket system or a phone call. Your own endpoint works too, at a public address: read the JSON body and act on status. Answer within 5 seconds, or the plugin records the message as failed.

To test the setup, break sending on purpose (a wrong SMTP password on a staging copy is the easy way) and press Send test now. A message should arrive within a few seconds. Under the Webhook URL field, the plugin screen shows the last message it sent: when, whether it was delivered, and the HTTP status or the error. Fix the setting and press Send test now again for the recovery message.