n8n Self-Hosting is a skill for Claude that takes a fresh Debian or Ubuntu server to a running, HTTPS n8n over SSH. It asks first whether you want single mode (one n8n with SQLite) or queue mode (a main process, Redis, Postgres and workers), then collects the domain, TLS email, timezone and SSH details.
It follows a fixed flow: preflight checks for DNS and ports, Docker install, project files, fresh secrets generated on the server, firewall, launch and verification. It also covers task runners for Python Code nodes, managed OAuth credential overwrites, updates, backups and restores.
What You Get
- A mode choice between single and queue, with the trade-offs and the RAM floor for queue
- Docker Compose templates for each mode, a Caddyfile for automatic HTTPS and example environment files
- A checklist that DNS points at the box and ports 80 and 443 are open before launch
- Secret generation on the server, a rule to back up the encryption key off the box and a grep that catches leftover placeholders
- Verification steps for health, certificate issue, public reachability and main and worker environment parity
- Reference files for security hardening, queue mode, task runners, credential overwrites and Day-2 operations
Common Use Cases
- Deploying n8n on a Hetzner, DigitalOcean or EC2 server with a domain and HTTPS
- Moving from a single instance to queue mode with workers
- Enabling Python Code nodes with a runners sidecar
- Updating, backing up or restoring a self-hosted n8n
- Setting up Sign in with Google without handing every user the OAuth client secret
What Makes It Unique
It covers the whole path from an empty server to a verified instance, including the early checks that catch a wrong A record or a closed cloud firewall. It treats the encryption key as the one secret that cannot be lost, tells Claude to claim the owner account before sharing the URL, and keeps queue workers and the main process on the same settings.
Under The Hood
The skill is instructions, six reference files and template assets. It has Claude connect to your server over SSH and run commands as root or a sudo user: it installs Docker with the official get.docker.com script, copies the compose, Caddy and environment files, generates secrets with openssl, edits the firewall with ufw, starts the stack with docker compose, and calls the health endpoints with curl. It writes files and changes server settings, and it fetches an installer script from the internet, so review each step against your server. One shipped shell script, init-data.sh, runs inside the Postgres container on first start in queue mode and creates the non-root database user from the password in your environment file. The Caddyfile and the example environment files are templates that hold placeholders and are filled in on the server.