Six outcome sources
Monitor published posts, email handoffs, WooCommerce orders, Action Scheduler jobs, named hooks, or custom heartbeats.
Automation monitoring / Built by Pixeldust
Verify that automated WordPress processes produced the result they were supposed to produce.
A completed task is not the same thing as a completed outcome.
The problem
A scheduler can fire while a post never publishes, an email never hands off, an order never appears, or an integration quietly stalls. Outcome Watchdog measures the expected result inside a fixed time window and records what actually happened.
What it does
Six practical capabilities, organized around the one job this plugin is meant to do.
Monitor published posts, email handoffs, WooCommerce orders, Action Scheduler jobs, named hooks, or custom heartbeats.
Set the expected count, recurring window, and grace period for late work.
Send email or JSON webhook notifications when a monitor fails and when it later recovers.
Trigger a namespaced action or outbound webhook while the connected workflow retains control of limits and locking.
Review dashboard status, manual checks, event history, Site Health integration, and retention controls.
Report custom outcomes through PHP, WP-CLI, a WordPress action, or a token-authenticated REST heartbeat.
How it works
Choose the real-world result, expected count, window, grace period, and evidence source.
Count qualifying outcomes while the monitoring window is open.
Classify the completed window after its grace period.
Alert on failure and confirm recovery with a later completed window.
The boundary
An email handoff does not prove inbox delivery, and a fired hook does not prove every downstream effect. The plugin also cannot alert while the entire WordPress stack is offline, so external uptime monitoring remains a separate job.