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, adds cron jobs, 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)
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.
Screenshots
A contact-form journey failing at step 6: every step has its own screenshot, so you see exactly where it broke.
Journeys suggested from your site, such as sign-in and product search, ready to switch on.
Health checks for the same site: HTTP status, DNS, SSL certificate, domain registration and blank-page detection.