Quick takeaways: n8n is a fair-code workflow automation platform with 400+ integrations and native AI capabilities according to its README. The official quickstart supports npx n8n for Node.js users and a Docker command with a persistent n8n_data volume. The editor runs at http://localhost:5678 in the documented quickstart.
What is n8n?
n8n is a workflow automation platform for technical teams that want no-code speed while still being able to write code when needed. The official README describes 400+ integrations, native AI capabilities, self-hosting, and a cloud option.
It is useful when you need to connect APIs, webhooks, databases, SaaS tools, and AI services into repeatable workflows.
When should you use n8n?
Use n8n when you have repetitive operations across multiple apps, need internal automation, want to self-host workflow data, or need a visual workflow builder with JavaScript/Python escape hatches.
Do not expose a quickstart instance directly to the internet without planning accounts, HTTPS, backups, environment variables, and access control.
Prerequisites
For the npx path, the README says Node.js is required. For Docker, you need a working Docker installation and an available port. The README uses port 5678.
You should also use persistent storage. The official Docker quickstart creates a volume named n8n_data and mounts it at /home/node/.n8n.
Quick start with npx
The README documents this instant trial command:
npx n8nThis is convenient for a development machine. For a long-running server, Docker or the official hosting docs are a better operational starting point.
Self-host n8n with Docker
Create the Docker volume first:
docker volume create n8n_dataThen run the container:
docker run -it --rm --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8nOpen the editor at:
http://localhost:5678On a VPS, localhost refers to the server. For remote access, plan a reverse proxy, HTTPS, and proper authentication.
A safe first workflow
Start with a Manual Trigger, add an HTTP Request node to call a test API, then add a simple processing or notification step. The goal is to understand how data moves between nodes before building complex automations.
If you test AI nodes or external APIs, use limited test credentials. Do not paste production secrets into an experimental workflow.
Verification
Verify that the container is running, the editor opens at http://localhost:5678, the n8n_data volume exists, and a test workflow can execute. Restarting the container should keep configuration if the volume mount is correct.
If the editor does not load, check port 5678, container logs, firewall rules, and any reverse proxy configuration.
Common issues
Forgetting persistent storage can lead to lost test data. Keep the n8n_data mount from the README quickstart.
Port 5678 may already be used. Change the host-side port mapping if needed.
Exposing n8n too early is risky because automation tools often store credentials. Add HTTPS, user management, and backups before public access.
License and legal notes
The README describes n8n as fair-code under the Sustainable Use License and n8n Enterprise License. It is source available and self-hostable, but commercial use should be checked against the official license terms.
FAQ
Is n8n fully open source?
The README describes it as fair-code and source available, distributed under the Sustainable Use License and Enterprise License. Review those terms for your use case.
Can I run n8n with Docker only?
Yes. The official README includes a Docker quickstart with a persistent n8n_data volume and port 5678.
Can n8n automate AI workflows?
The README mentions native AI capabilities. Manage API keys, permissions, and provider costs carefully.
