External reliability monitoring for n8n

Know the moment your automations stop working — even when n8n says success.

MateSentry watches your n8n workflows from the outside: missed runs, failure spikes, silent workflows, and successes that never produced the expected business outcome.

Start monitoring See pricing

What MateSentry answers

Is it running when expected?

Scheduled workflows are checked against their configured cadence; non-scheduled workflows use a learned baseline that only alerts once it is mature.

Is it failing or degrading?

Failure-rate spikes, repeated identical error fingerprints, abnormal durations and unexpectedly low volume are all deterministic rules.

Did the business outcome happen?

An optional Outcome Beacon lets a workflow confirm it reached your real success checkpoint — not just an n8n success status.

Is the instance reachable?

Connection failures, disabled Public APIs and monitored workflows that quietly become inactive are surfaced as incidents.

Explained, not guessed

Deterministic rules decide that an incident exists. AI only explains redacted evidence, and never changes severity or status.

Read-only by design

MateSentry uses read endpoints of the n8n Public API. It never edits, activates, retries or deletes anything in your instance.

Honest health states

Every monitored workflow always shows exactly one state — including when MateSentry does not yet know enough to judge it.

Healthy

Behaving within its established baseline.

Warming Up

Collecting history — baseline is not mature enough to alert.

Warning

A deterministic rule matched at warning severity.

Critical

A deterministic rule matched at critical severity.

Paused

Monitoring is intentionally paused or muted.

Unreachable

MateSentry cannot reach the n8n instance.