Deploy n8n in one click on TheCodexApps
A practical walkthrough of running your own n8n automation instance: picking a package, deploying from the Apps catalog, custom domains with SSL, the environment variables that matter, backups and updates.
TheCodexApps Team
n8n is a workflow automation tool you can self-host: a visual editor where you wire triggers (webhooks, schedules, email) to actions (HTTP requests, databases, spreadsheets). It is the open-source backbone behind a lot of internal automation, and because it is just a Node.js application with a database, it runs well on a small server. This guide walks through deploying it on TheCodexApps from the Apps catalog and then running it like a production service: with a custom domain, SSL, persistent data and a sane update routine.
What n8n actually needs
Before clicking anything, it helps to know what you are sizing. An n8n instance is:
- a Node.js web process serving the editor and the REST API,
- a workflow database (SQLite by default, Postgres or MySQL optional),
- a queue for executions (optional, only needed at higher scale),
- persistent storage for credentials and binary data.
For personal automation — a handful of workflows firing a few hundred executions a day — 1 GB of RAM is workable. Once you add scheduled workflows, webhook-heavy integrations or a team editing at the same time, 2 GB gives you comfortable headroom. CPU is rarely the bottleneck; memory and disk are.
Choosing a package
TheCodexApps packages pool resources you can split across as many apps as you like. A 2 GB package comfortably runs n8n plus a small Postgres instance for its data, with room left for a status page or a static site. If you plan to run n8n alongside several other services, start at 4 GB and watch the memory meters in the panel for a week — you can upgrade whenever you need to, and the upgrade is prorated.
Deploying from the Apps catalog
- Create an account and pick a package (or start on the free tier to look around).
- Open Apps in the panel and find n8n in the catalog.
- Click deploy. TheCodexApps provisions the container, registers a free subdomain and issues a TLS certificate automatically.
- When the status turns green, open the URL and create your local n8n owner account.
That is the whole "one click" part. The rest of this guide is about turning that fresh instance into something you can rely on.
Custom domain and SSL
The default subdomain works fine, but most people eventually want automation on their own domain, for example automation.example.com:
- Add a DNS record pointing the hostname at your location's server (an A record, or a CNAME to the default subdomain).
- Add the domain in the service settings in the panel.
- SSL is issued and renewed automatically — no certbot, no manual renewal.
Environment variables that matter
n8n keeps its configuration in environment variables. The two you should set on day one:
N8N_ENCRYPTION_KEY=<long random string>
WEBHOOK_URL=https://automation.example.com/
- N8N_ENCRYPTION_KEY encrypts the credentials n8n stores (API keys, database passwords). Set it once, before you save any credentials, and store a copy somewhere safe: without it, a restored backup cannot decrypt your credentials.
- WEBHOOK_URL tells n8n how to build the public URLs it hands out for webhook nodes. If you change your domain later, update this variable too, or existing webhook triggers will advertise the old host.
If you use n8n's editor heavily behind a reverse proxy, N8N_HOST and N8N_EDITOR_BASE_URL are worth a look as well.
Persistent data and backups
Everything n8n knows — workflows, credentials, execution history — lives in its data directory. On TheCodexApps that directory persists across restarts and redeploys, so a normal update never costs you your workflows. Backups are taken on a schedule and stored off-server; you can also export individual workflows as JSON from the n8n editor at any time, which is a good habit before big changes.
If you want execution history to survive a long time on a small package, either prune old executions in n8n's settings or point it at a Postgres database instead of SQLite — the panel's one-click Postgres makes that a five-minute change.
Updating n8n
n8n moves fast, and updates regularly fix security issues in node integrations. The upgrade path is deliberately boring: trigger a redeploy from the panel and the service pulls the new image version while keeping the data directory and environment variables in place. Read n8n's release notes before major version jumps (they occasionally change node behavior), export the workflows first, and redeploy during a quiet window. If something breaks, restore the backup taken before the update.
A note on licensing
n8n is source-available under the Sustainable Use License. Running it to automate your own company's processes is exactly the intended use; embedding it into a product you resell is restricted. If your automation stays internal, you are fine — and if you are unsure, read the license text or ask on their forum before building a business on top of it.
Wrapping up
A self-hosted n8n instance is one of the highest-leverage small servers you can run: it quietly saves hours every week. Deploy it from the catalog, set the encryption key and webhook URL, put it on a real domain, and treat updates as routine. From there, the only hard part is deciding what to automate first.