FAQ
Webhook Disable Monitor for WooCommerce (pre-release)
Is it available now?
No. It is a pre-release that has only been tested in local test environments. It is not on WordPress.org yet and there is no download.
Will the plugin be free?
Yes. Monitoring, the admin page, the admin notice and the notification e-mail attempt are planned to be free under the GPL. A paid add-on is only being evaluated.
Does it bring my webhook back automatically?
No. It never reactivates, edits, resends or replays webhooks. You fix the receiving endpoint and reactivate the webhook yourself in WooCommerce.
Will I get the orders that were missed while the webhook was disabled?
No. WooCommerce does not queue them and this plugin does not store or replay them. You need to reconcile them in the receiving system.
Does it stop webhooks from failing?
No. It tells you after WooCommerce has disabled a webhook. It does not change the failure threshold or keep a failing webhook active.
Is the alert e-mail certain to arrive?
No. The plugin attempts to send one notification per episode through WordPress's wp_mail(). The admin page shows one of these states: Accepted by WordPress (wp_mail() returned success; this does not confirm inbox delivery), Failed (wp_mail() returned false or reported an error; only a generic code is kept), Pending (the attempt did not finish, for example because PHP stopped; it is not retried), Captured locally (not sent) (test environments with the WDMFW_CAPTURE_MAIL constant only) or Not sent: no valid recipient. Delivery depends on your site's mail setup (SMTP plugin, host, spam filters).
How many e-mails will I get?
The plugin attempts to send one notification per disable episode. Further failure signals for the same episode are counted on the admin page and do not trigger another attempt. Whether the attempt reaches your inbox depends on your mail setup.
Who is the e-mail addressed to?
The site administrator e-mail address configured in WordPress (a developer filter can change the recipients). If no valid recipient exists, the status is "Not sent: no valid recipient".
What data does it store?
Webhook ID, topic, counts, last response code, timestamps, episode and e-mail status, and the endpoint reduced to scheme, host and port, with the host possibly shown as [host redacted]. The URL path, query string, fragment, username and password are discarded before storage. The webhook name, payloads and customer data are not stored. Everything stays in your WordPress database. WooCommerce itself still keeps the full URL and webhook name in its own delivery log and webhooks table.
Why does it show [host redacted]?
Hostnames can contain tokens in subdomains, and no pattern can recognise every secret, so the plugin does not try to detect them. It keeps a host only if it is on an allow-list: the registrable domain, the registrable domain plus one of www, api, hook, hooks, webhook or webhooks, an allowlisted automation host (Zapier, Make, extendable by filter), localhost, or a private, loopback or reserved IP. Everything else, including public IPs, is redacted; the port is kept.
Can anything sensitive remain visible?
Yes, in limited ways. A registrable domain, a safe label or an allowlisted host stays visible, and a domain can itself be identifying or sensitive. Private IPs and ports stay visible. WooCommerce's own delivery log and webhooks table, which this plugin does not control, keep the full URL and the webhook name.
Does it send anything to you or to third parties?
No. It makes no external calls. The only outgoing message is the alert e-mail sent by your own site through wp_mail().
Does it work with HPOS?
It was tested with HPOS on and off on WooCommerce 11.2.2 and 11.3.0-rc.2.
Which versions are supported?
Only what was tested: WordPress 7.1.4; WooCommerce 11.2.2 and 11.3.0-rc.2; PHP 8.1 and 8.4; SQLite and MariaDB 11.4. MySQL, multisite, object caches and other versions have not been tested.
What are the known limitations?
Reactivating a webhook directly in the database can cause the next disable to be missed; a 300-second window treats quick reactivate-and-disable cycles as repeats; an e-mail can be lost if PHP dies mid-send; there is no replay and no delivery guarantee.
Do Zapier, Make or uptime monitors already cover this?
Not directly. Zapier and Make alert you about errors inside a Zap or scenario, but a disabled WooCommerce webhook sends nothing, so there may be nothing to alert on. Uptime monitors check whether a URL responds, not the webhook status inside WooCommerce. Other plugins exist: some add retries, a delivery history and replay (for example WebhookGuard, free), others monitor webhook status on a schedule (for example Hookniva, free and also read-only) or offer extra alert channels and manual retry (for example WPStore+ Webhook Delivery Monitor, listed at US$39/year). This plugin reacts to WooCommerce's own disable action, stays read-only and does not keep payloads, webhook names or non-allowlisted hosts. Compare them for your needs.
Is there a paid version?
Not yet. A premium add-on is under evaluation. There is no checkout, no pre-sale and no payment. See the pricing page for the ideas being tested.
Do I need to talk to anyone?
No. There are no calls or demos. Documentation is written; support for the free plugin will be through its public support forum once published.