Email Check plugin: set up alerts

The nanoPost Email Check plugin can send a failed-test alert to Slack, Google Chat or Discord, so you can see it without opening WordPress. The alert uses a web request and does not depend on the site’s email sending working.

To connect a service, you create a webhook URL: a special address that accepts messages for your chosen channel or space. Paste that address into Tools > Email Check > Webhook URL and save. The sections below explain where to get it.

This is optional. Leaving the field empty disables webhook alerts; dashboard warnings and test emails still work. Keep the URL private, like a password, because someone with it can post messages to that destination.

Choose your service: Slack, Google Chat or Discord. If you manage an automation or a custom receiver, the technical details are further down.

Slack

  1. Open Slack’s app creation screen, create an app and select the workspace where you want alerts. You are creating a connection for these messages; this setup does not require writing code.
  2. In the app’s settings, open Incoming Webhooks and turn on Activate Incoming Webhooks.
  3. Select Add New Webhook to Workspace, choose the channel and authorise the connection.
  4. Copy the generated URL. In WordPress, paste it into Tools > Email Check > Webhook URL and click Save Changes.

If workspace permissions prevent creating or installing the app, ask your Slack administrator to help. Slack’s webhook instructions show the setup screens.

Google Chat

You need a Google Workspace Business or Enterprise account whose organisation allows incoming webhooks. Set this up in Chat in a browser.

  1. Open the space where you want alerts. Next to its title, open the menu and choose Apps & integrations, then Add webhooks.
  2. Give the webhook a name, such as Email Check, and save it.
  3. Use the webhook’s More > Copy link option to copy its URL.
  4. Paste it into Tools > Email Check > Webhook URL in WordPress and click Save Changes.

If the add button is unavailable, ask your Workspace administrator whether incoming webhooks are allowed. Google’s setup instructions describe those requirements.

Discord

Create a webhook in the channel’s Integrations settings and copy its URL. Add /slack to the end of that URL before pasting it into Tools > Email Check > Webhook URL, then save.

The suffix selects Discord’s Slack-compatible receiver, which accepts the message format Email Check sends. Discord documents this in its webhook reference.

What you will receive

A failed test produces a message containing your site address and the error. For example:

Email check failed on https://example.com: SMTP Error: Could not authenticate.

Every failed check attempts an alert, including tests started with Send test now. When a destination has received a failure alert, the first later passing test attempts a recovery message:

Email check passed again on https://example.com.

After a recovery message is delivered, further passing tests send nothing. If the recovery message cannot be delivered, the next passing check tries it again. Changing the URL starts fresh: the new destination does not receive a recovery message for a failure reported to the old one.

These alerts depend on a check producing a result. They do not warn you when the scheduled check never runs or crashes before producing one. The separate automatic-checks warning appears in WordPress.

Check that alerts reach you

Saving a webhook URL does not send a test alert. An ordinary passing email test does not send one either, unless it is recovering from a failure that this destination received.

If your site currently has a failed email test, save the URL and run Send test now. If the test fails again, look for the alert in your channel or space. Under Webhook URL, Email Check reports the most recent alert attempt, including whether the receiver accepted it or an error occurred.

If email is working, use a staging copy, a separate site for testing changes, to try the failure-and-recovery sequence. Set the webhook there, temporarily make the staging site’s sending credentials invalid, and run a test. Restore the credentials and test again. Look for both messages, and leave the staging site’s sending settings as you found them. Do not break live sending to test an alert.

If an alert does not appear, first check the delivery status below the URL field. If the receiver rejected it, keep that status or error for the service’s support team. If it was accepted, check that you are looking in the channel or space associated with that URL. The status describes the web request; seeing the message confirms it reached the place you monitor.

Custom receivers

An automation service or your own endpoint can receive the alert and act on it. This section is for whoever configures that receiver; the Slack, Google Chat and Discord setups above do not require you to build one.

Email Check sends an HTTP POST with a JSON body, a structured set of named values. The content type is application/json; charset=utf-8. A failure payload looks like this:

{
  "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 Meaning
text The readable alert message
site The site’s home URL
status fail for a failure, or pass for recovery
error The error text; empty on recovery
time The check time in ISO 8601 format, using UTC

For Google Chat URLs, the plugin sends only text. A failure without an error message uses the text wp_mail() returned false and gave no error message.

Return a successful HTTP response, with a status in the 200–299 range, within five seconds. Email Check records other responses and timeouts as failed alert deliveries.

The URL must pass WordPress’s safe-request validation. In a default setup that means a public HTTP or HTTPS address on port 80, 443 or 8080. A private-network receiver or a service on another port needs an accessible endpoint that meets those requirements. If saving the URL produces a validation error, the previous URL is kept.

If you are still choosing which mailbox receives test emails or how often they run, the Email Check setup page takes you through those settings.