Scheduled monitoring shrinks that window. NorthDuty Connect closes it. It's a free plugin we've just released that notifies NorthDuty the instant something on your site changes — so instead of waiting for the next scheduled slot, your checkout journey, form submissions, visual baselines, and health checks re-run right now, while the update is still fresh and the rollback is one click.
What it does
NorthDuty Connect listens for the moments WordPress sites actually break and sends NorthDuty a small, signed notification for each one:
Updates — including the automatic ones. Plugin, theme, and core updates, whether you clicked them in a maintenance window or WordPress applied them at 3am. This is the headline event: update-day is when checkouts break, and an update-triggered journey run means the break is caught minutes after it happens.
Activations, deactivations, and theme switches. The other ways the built site changes without a deploy pipeline ever knowing.
Published content changes. Posts, pages, and WooCommerce products — so a visual baseline refresh and a page check follow real edits. Drafts, autosaves, and revisions are deliberately ignored; nothing a visitor can't see triggers anything.
When NorthDuty receives the event, it re-runs the checks that matter for your project: real-browser journeys through checkout, login, and forms; pixel-diff comparisons of your key pages against the previous baseline; and the full health check — uptime, SSL, JavaScript errors, and the API endpoints your pages depend on.
What it deliberately doesn't do
The plugin is intentionally tiny — around 580 lines of plain PHP with no third-party code. It adds no dashboards to wp-admin, runs nothing on your visitors' page views, sets no cron jobs, and stores nothing about your users. Every notification is a fire-and-forget request with a two-second timeout, so it cannot slow your site down even if NorthDuty were unreachable — your scheduled checks continue regardless; the plugin only makes them faster to react.
Each event contains just the event type, your site URL, the changed item's permalink and ID where relevant, and the plugin version — HMAC-signed with a secret only you and NorthDuty hold, so the endpoint can verify every delivery actually came from your site. No visitor data, no account data, no content bodies, ever.
We tested it the honest way
The first production test of NorthDuty Connect was on Summit & Trail Outfitters, the real WooCommerce store we run as a live demo — during the WordPress 7.1 core update, on the day 7.1 shipped. The update finished, the plugin fired its core.updated event, and the deployment appeared in the project's activity feed seconds later with the full check run queued behind it. That's the exact loop your sites get: update lands, checks run, and if the checkout had broken, the alert would have named the failing step with a screenshot before anyone finished reading the update changelog.
Setting it up takes about two minutes
- Install the plugin and activate it (download below, or from the WordPress.org directory once it completes review).
- In NorthDuty, open your project's Settings → Deploy detection and copy the webhook address and signing secret. Don't have a project yet? A free account takes a minute — no card.
- In wp-admin, go to Settings → NorthDuty, paste both values, and save.
- Click Send test event. You'll see the delivery confirmed on both sides — then update a plugin and watch the checks fire.
That's the entire integration. No API keys to scope, no code, nothing to maintain.
Get the plugin
NorthDuty Connect is available on the WordPress.org plugin directory — install it from wp-admin via Plugins → Add New (search "NorthDuty Connect"), and you'll get updates through wp-admin like any other plugin. Prefer a manual install? You can still download the zip directly. It's free and GPL-licensed either way.
Who this is for
If you run a single WooCommerce store, the plugin turns "I hope that update didn't break checkout" into a verified answer within minutes — see WooCommerce monitoring for what runs on a store.
If you're an agency on retainers, it changes update day across the whole roster: batch your updates, and every client site verifies itself as its window closes — the workflow we describe in monitoring multiple WordPress sites. Install the plugin on each client site, point each at its own NorthDuty project, and the "who checks the sites after updates?" question answers itself.
And if your site is custom, headless, or not WordPress at all — the same webhook works from any CMS or CI pipeline. The plugin is simply the zero-effort version for the platform where updates cause the most surprises.