Most WordPress breakage follows an update. A plugin auto-updates overnight, the checkout hook changes, a button stops working \u2014 and the site keeps returning HTTP 200 the whole time, so uptime monitoring sees nothing.<\/p>\n\n
NorthDuty Connect closes that gap. It notifies NorthDuty<\/a> the moment something on your site changes, and NorthDuty immediately re-runs the checks that matter instead of waiting for the next scheduled slot:<\/p>\n\n 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 \u2014 nothing here slows your site, adds cron jobs, or stores visitor data.<\/p>\n\n What triggers a notification<\/strong><\/p>\n\n See it in action<\/strong><\/p>\n\n 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<\/a>.<\/p>\n\n 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<\/strong>. Until then it sends nothing.<\/p>\n\n Each notification contains: the event type (for example 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<\/a> and Privacy Policy<\/a>.<\/p>\n\n\n\n
\n
External services<\/h3>\n\n
plugin.updated<\/code> or page.published<\/code>), 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.<\/p>\n\n