n8n: The term ‘n8n’ is not recognized as the name of a cmdlet, function, script file, or executable program. Check if you spelled the name correctly, or if you included a path, verify that the path is correct and try again.
Line: 1 Character: 1
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
welcome to the n8n community @Henry_Florian
I’ve seen this before—it usually just means n8n didn’t install correctly or isn’t in your system PATH yet.
Personally, I’d start by making sure Node.js and npm are actually responding (try node -v and npm -v). If they are, I usually just run a global install: npm install -g n8n.
If n8n start still doesn’t work after that, try closing and reopening your terminal. On Windows especially, the PATH doesn’t always update until you start a new session. If it’s still acting up, I’d check npm config get prefix to see where your global modules are living and make sure that folder is actually in your system PATH. That’s almost always the culprit.
Hi @Henry_Florian Welcome!
Have you tried npx n8n? Or something like a manual path assistance, where you run this command npm config get prefix and take the output path append a \ in there and then just manually add it to your windows env variable, and then just type n8n start after a restart and things should be working fine, let me know how it goes with these.