Know the day a workflow goes quiet — not the week after.

A trigger with an expired login stops without an error, and n8n sends nothing. Guard learns how often each of your workflows usually runs and messages you when one goes quiet, keeps failing, or comes back. It also tells you which workflows would send, pay or delete with nobody asked.

How it decides

Quiet

Nothing ran for three times the workflow’s usual gap (never under an hour, never over a week). Runs you started by hand don’t count toward the rhythm.

Failing

Three of the last five runs failed, or the last two did. One message when it starts, one when it recovers — not one per failure.

Would run without asking

Each workflow is read the same way as on the checker: steps that can’t be undone and have no approval in front of them are listed, with a one-click copy that asks first.

Rather keep it inside your own n8n?

Take the free Quiet watchdog workflow: every 30 minutes it lists your active workflows and recent executions, and emails you the ones that have not run for longer than a threshold you set (per workflow with [quiet:24h] in the name). It needs an n8n API credential and your Gmail. The hosted Guard above does the same without a fixed threshold — it learns each workflow’s rhythm — and adds the “would run without asking” check.

What we store

Your n8n address, the API key (encrypted; it is only ever used for GET requests), the message address you gave, and the last check’s result (workflow names, states, timestamps). No execution data, no inputs. “Stop watching” deletes all of it.