Fix · n8n
n8n: How to Check If a Workflow Is Running Without Logging In
Need to confirm an n8n workflow is running from outside? Here are 3 methods that work.
Quick diagnostic
Three things to check first
Check the trigger
Look at the last successful run. If the trigger hasn't fired since, the issue is upstream — a webhook URL changed, a cron schedule was edited, or the source system stopped sending events. Start here before you look at the workflow itself.
Check the credentials
OAuth tokens expire quietly. API keys get rotated by a teammate who didn't know they were in use. A service account password changes upstream. Re-connect the integration that touches the step where the chain broke and try again.
Check the logs
Open the most recent failed run. The first red step is where the chain broke — usually a field name that changed in the source data, a rate limit that kicked in, or a timeout talking to a downstream service. Fix that one step and the rest of the chain usually recovers on the next run.
Logging into every client's n8n instance every morning to confirm
the overnight runs completed is a habit that doesn't scale past
about five clients. If you're past that, you need a way to check
workflow state without clicking into n8n at all.
The API-based method uses n8n's own REST API. GET
/api/v1/executions?workflowId={id}&limit=1 returns the most recent
run; you check the startedAt field against what you expected. This
works on n8n Cloud and self-hosted alike and takes about 30 lines
of code to wrap into a script. The weakness is that it assumes n8n
itself is reachable — if the instance is down, your script gets a
connection error and you have to interpret that separately from
"workflow didn't run."
The webhook-ping method works for trigger webhooks specifically.
You pick a simple GET endpoint n8n exposes (or a trivial workflow
that returns 200) and point an external URL-check service at it.
If the webhook URL stops responding, you get notified. This catches
instance-level failures but doesn't help for scheduled triggers or
polling triggers.
The third method is to skip building this entirely and use a
service that does it for you — watches execution history, watches
instance reachability, watches credentials, rolls it all up into a
plain-language morning message. For an agency managing multiple
clients, that's cheaper than the engineering time it takes to
maintain a homegrown version.
The pattern
Most of these fail quietly.
Here’s the pattern: most automation and vibe-coded apps fail quietly. No alert, no error — just silence, until a customer notices. NoCrash watches your tools from outside and tells you in plain language, every morning, what ran clean and what didn’t. Peace of mind, not a log dump.
Stop finding out from your customers.
One morning message telling you what ran clean and what didn’t. Free forever on 3 things to watch.
Common questions