whatsapp-monitor

WhatsApp monitor — catch a connected-but-deaf channel

Every 5 minutes: compares the WhatsApp store with what wfnexus has heard, checks the last receive, failing or stuck subscriptions and unknown self ids, and alerts the owner’s chat through whatsapp-sender when it is deaf.


Source	`templates/whatsapp-monitor/workflow.yaml`
Category	`debugging-ops`
Trigger	manual (`wfx run`) · schedule `/5 * * *`
Steps	3
Human approval before	none
Providers named	default (`WFX_DEFAULT_PROVIDER`)

Use it

wfx templates whatsapp-monitor
wfx new whatsapp-monitor --as my-whatsapp-monitor
wfx dryrun my-whatsapp-monitor

What it does

Checks that the WhatsApp channel is actually receiving: store-vs-wfnexus lag, last receive time and error, failing or stuck subscriptions and unknown self ids. Alerts the owner’s chat through whatsapp-sender when something is wrong.

What you fill in

input owner_chat default: the owner’s WhatsApp JID (the alert goes there)
env WA_CHANNEL: the channel name from registries.json
env STORE_PROBE: a read-only command printing {“latest”: “<iso time>”} for the newest message in the WhatsApp store (without it, lag is not measured)
copy whatsapp-sender too — the alert goes through it

Inputs

Input	Type	Default	Required	Meaning
`owner_chat`	string	`""`
`dry_run`	boolean	`false`

Steps

#	Step	Kind	Skills	Gates
1	`check` Check that WhatsApp is hearing	shell (`run:`)		`exitCode` = `2` → fail
2	`alertkey` Dedup key for the alert	shell (`run:`)
3	`alert` Alert the owner through whatsapp-sender	agent

Human gates

This template never stops for a person.

Real result