NorthDuty Connect – Checkout, Form & Uptime Monitoring

By northduty

0+ active installationsVersion 1.3.1

Re-runs your NorthDuty checks the moment a plugin, theme, or core update lands — a broken checkout or form is caught in minutes, not by a customer.

Description

Most WordPress breakage follows an update. A plugin auto-updates overnight, the checkout hook changes, a button stops working — and the site keeps returning HTTP 200 the whole time, so uptime monitoring sees nothing.

NorthDuty Connect closes that gap. It notifies NorthDuty the moment something on your site changes, and NorthDuty immediately re-runs the checks that matter instead of waiting for the next scheduled slot:

  • Real-browser journeys — your checkout, login, signup, and contact-form flows, run step by step, with the failing step named and screenshotted.
  • Website health checks — uptime, SSL, DNS, blank pages, JavaScript errors, and the API endpoints your pages depend on.

The plugin itself stays deliberately tiny: it listens for update and content events and sends a small signed notification. All monitoring runs on NorthDuty’s infrastructure — nothing here slows your site or stores visitor data.

What triggers a notification

  • Plugin, theme, and core updates — including automatic background updates
  • Plugin activation and deactivation, and theme switches
  • Published content changes: posts, pages, and WooCommerce products (drafts, autosaves, and revisions are ignored)

Test mode (optional, off by default)

Switch on test mode and a NorthDuty journey can finish a WooCommerce checkout or submit a contact form on your live site without side effects. A journey proves it comes from your NorthDuty project with a short-lived token signed by your signing secret. Only for those requests:

  • WooCommerce offers a “NorthDuty test payment” method that takes no money and leaves the order unpaid
  • Orders the journey places are marked as test orders: no stock is reduced, no webhook is delivered, and they are deleted about ten minutes later
  • No email is sent, unless you switch on the optional mail server check: then one test email per form journey goes to an address you choose
  • Forms built with Contact Form 7, WPForms, Fluent Forms, Ninja Forms or Forminator can be submitted: the stored entry (Flamingo for Contact Form 7) is deleted with the test orders
  • A submitted form must try to send its notification email. The email is counted, not sent; if the form accepts the message and hands WordPress no email at all, the journey fails, so you find out when a notification has been switched off or deleted
  • The CAPTCHA is skipped on all five form plugins (Fluent Forms needs 6.0.3 or newer). Contact Form 7, WPForms and Fluent Forms also skip their spam checks

Real visitors never see the test payment method, and every protection stays on for them.

See it in action

We keep a real WooCommerce store that we break on purpose, so you can watch a monitored checkout fail and get caught: northduty.com/demo.

External services

This plugin sends event notifications to NorthDuty (northduty.com), a website monitoring service, only after you configure a deploy hook URL on the settings screen. Until then it sends nothing.

Each notification contains: the event type (for example plugin.updated or page.published), your site URL, the changed item’s permalink and ID where relevant, and the plugin version. Notifications are HMAC-signed with the secret you configure. No visitor data, user accounts, or content bodies are ever sent.

A NorthDuty account is required to receive the notifications. It works on every NorthDuty plan, including the free one. See NorthDuty’s Terms of Service and Privacy Policy.

Installation

  1. Create a free NorthDuty account at northduty.com (no card) and add your site as a project.
  2. In NorthDuty, open Settings → Run on site changes. On a WordPress site, the “Connect your WordPress site” card has the webhook address and a button to generate the signing secret. (Both are also under “Advanced: webhook & extra pages”.)
  3. Install and activate NorthDuty Connect, then paste both values under Settings → NorthDuty and save.
  4. Click “Send test event”. It shows up in NorthDuty under Recent changes.

FAQ

Does this plugin slow my site down?

No. Notifications are sent asynchronously with a short timeout and no retries, and nothing runs on page views by visitors. The monitoring itself happens entirely on NorthDuty’s servers, from the outside.

Does it work with WooCommerce?

Yes — that’s the main use case. Product changes trigger re-checks, and NorthDuty runs your actual cart and checkout flow in a real browser on a schedule. The plugin works on any WordPress site, WooCommerce or not.

Do I need a NorthDuty account?

Yes. The plugin only sends notifications; the checks themselves run in NorthDuty. Without an account and a configured webhook address, the plugin sends nothing.

Do I need a paid NorthDuty plan?

No. On the free plan, every update the plugin reports gets a health check, and your journey re-runs on up to 3 updates a day (after that, it waits for its daily schedule). Paid plans, from $29/month, re-run every journey on every update and add more journeys, faster schedules and detection that works without a plugin.

Does it work if my site is behind Cloudflare or a firewall?

The plugin sends outgoing requests only, so firewalls that filter incoming traffic don’t affect it. For NorthDuty’s checks to reach your site, a strict bot-protection rule may need to allow NorthDuty’s monitoring traffic. NorthDuty reports a blocked check as blocked rather than as a broken site.

Can I use it on a staging site?

Yes. Add the staging site to NorthDuty as its own project; it gets its own webhook address and secret, so staging and production are monitored separately.

What happens if NorthDuty is unreachable?

Nothing visible: the notification is dropped and your site carries on. NorthDuty’s scheduled checks still run regardless — update-triggered re-checks are an acceleration, not a dependency.

What does test mode change for my customers?

Nothing. The test payment method, the skipped CAPTCHA and the muted emails apply only to requests that carry a valid token signed with your signing secret. Without the token the site behaves exactly as before.

Does the form check prove my notification emails arrive?

By default it proves the form tried to send one; nothing is actually sent during a journey. Fill in “Mail server check” in the plugin settings to go one step further: the first email of each form journey is then really sent, to the address you enter instead of its usual recipients, and the journey fails if your mail server refuses it (wrong SMTP password, expired API key, sending limit reached). It does not prove the email reached an inbox rather than a spam folder; look at the mailbox you entered for that. If a form is meant to send no email, turn the check off with the ndconnect_require_form_notification filter.

Which forms can a journey submit?

Forms built with Contact Form 7, WPForms, Fluent Forms, Ninja Forms and Forminator. A CAPTCHA (reCAPTCHA, hCaptcha or Turnstile) is skipped on all five, for NorthDuty journeys only; Fluent Forms needs 6.0.3 or newer. On Ninja Forms and Forminator the journey is shown the form without its CAPTCHA field.

Do test orders show up in my reports or reduce stock?

Test orders stay unpaid (pending), never reduce stock, trigger no WooCommerce webhook, and are deleted permanently about ten minutes after the journey places them.

Screenshots

Changelog

1.3.1

  • Improved: the mail server check now sends the notification meant for the site owner. A confirmation addressed to the visitor is only used when the form sends nothing else.

1.3.0

  • New: optional mail server check. Enter a test address and the first email of each form journey is really sent to it, so a journey fails when your mail server refuses the form’s notification. All other email stays muted.

1.2.2

  • New: in test mode, Ninja Forms and Forminator forms protected by reCAPTCHA, hCaptcha or Turnstile can be submitted by NorthDuty journeys. Real visitors still get the CAPTCHA.

1.2.1

  • New: in test mode, Fluent Forms (6.0.3 or newer) skips reCAPTCHA, hCaptcha and Turnstile, and its Akismet and CleanTalk checks, for NorthDuty journeys only.

1.2.0

  • New: test mode now covers forms built with WPForms, Fluent Forms, Ninja Forms and Forminator, as well as Contact Form 7. Entries a journey creates are deleted about ten minutes later.
  • New: a journey fails when a form accepts a submission without trying to send a notification email. Emails are still never sent during a journey.

1.1.1

  • Fix: NorthDuty is now told about test mode when the deploy hook URL or signing secret is changed while test mode is already on. Before, you had to switch test mode off and on again, or send a test event.

1.1.0

  • New: optional test mode. NorthDuty journeys can place WooCommerce test orders and submit Contact Form 7 forms on the live site: no payment, no email, no stock change, and the test data is deleted automatically.

1.0.2

  • Works on NorthDuty’s free plan: every update gets a health check, and your journey re-runs on up to 3 updates a day.
  • Settings screen points to the current place in NorthDuty (Settings → Run on site changes) and links to sign-up.
  • Readme: screenshots and more FAQs.

1.0.1

  • Renamed all functions, options, and constants to the longer ndconnect_ / NDCONNECT_ prefix to avoid conflicts with other plugins.

1.0.0

  • Initial release: update, activation, theme-switch, and content-change notifications with HMAC-signed delivery and a settings-screen test button.