Free tool · runs in your browser
n8n workflow
checker.
Paste a workflow exported from n8n and the checker lists the faults that are easy to ship without noticing. Each one names the node and says what can go wrong. It is a kinder way to find them than a customer’s email.
Nothing is uploaded. The check runs on this page, in your browser. The workflow you paste is not sent to us or anywhere else, and it is not stored or logged. The visit to this page is counted like a visit to any other page here.
What it checks
- Credentials or secrets left in the JSON
- A webhook without authentication
- Retry On Fail on a node that writes or sends
- Google Sheets append where two runs can overlap
- No error branch and no error workflow
- Pinned data left in
- A Wait of five minutes or more feeding a send without a fresh read
Every n8n export names the credentials it uses and their ids, but never the secret itself. The checker only flags a credential name when it contains an email address, because that says whose account it is.
What it cannot tell you
The checker reads the structure of the file and nothing else. It cannot run the workflow or see your credentials. That means it cannot know whether a later node checks a secret behind an open webhook, or whether a retry is safe because the call carries its own key. Treat each finding as a place to look. Where a finding links to a note, the note says what we ran or read.
Some of these checks come from faults we hit or tested for in our own templates, one comes from reading n8n's code, and the others are ordinary good practice. For the checks that have a note in the library, the note tells you which of those it rests on and what we ran.