n8n is a workflow auto­ma­tion tool that lets you connect different apps and services with each other. CasaOS allows you to install and manage n8n using a simple web interface rather than working in Docker. In this guide, you’ll learn how to install n8n on CasaOS step by step.

Step 1: Check re­quire­ments and choose the right server

Before you install anything, make sure you have a server that’s powerful enough to run CasaOS and n8n. You’ll need:

  • Linux server (ideally with Ubuntu 22.04 or 24.04)
  • Root access or sudo per­mis­sions
  • A stable internet con­nec­tion
  • Optional: a domain for external access later

n8n can run on modest hardware, but the right setup depends on how you plan to use it. A few personal workflows need much less power than a live setup with several auto­ma­tions running at the same time. The following scenarios can help you choose a suitable starting point.

Tip

n8n is not the only auto­ma­tion platform out there. Other options include Zapier and Make. Zapier and Make focus heavily on easy cloud-based auto­ma­tion, while n8n gives you more control and flex­ib­il­ity through self-hosting. If you’re already using Zapier, migrating to n8n gives you more control over your data, workflows and costs.

Use case 1: Personal use or light­weight auto­ma­tions

If you want to use n8n by yourself, a modest server setup is usually enough. This works well for auto­mat­ing emails, social media tasks, RSS feeds as well as API con­nec­tions or no­ti­fic­a­tions. These n8n workflows are simple in nature and don’t run con­tinu­ously at a high frequency. Here the server load remains low, so you usually do not need much CPU, RAM or storage. RAM is more important than raw CPU power because CasaOS and n8n both need enough memory to run smoothly.

Use case 2: Startups and regular auto­ma­tions

For startups, side projects or teams that plan to use n8n more regularly, it’s worth planning for a little more per­form­ance. Once several workflows run in parallel or external APIs are used more often, your server has to handle a higher load. Typical uses cases include automated lead pro­cessing, CRM syn­chron­isa­tion or simple internal tools. More CPU cores and extra RAM keep n8n re­spons­ive. If you plan to expand your setup later, choosing a server with a bit more headroom from the start is usually the better option.

Use case 3: Business workflows with regular daily use

Small and medium-sized busi­nesses often use n8n for recurring business tasks. These can include automated data flows, in­teg­ra­tions between systems or internal workflows. Stability is crucial here. More RAM ensures that multiple processes can run at the same time without bot­tle­necks. You should also plan enough storage space, es­pe­cially if your workflows process logs, files or larger amounts of data.

Use case 4: High-volume workflows and heavier workloads

If you use n8n heavily, choose a more powerful system. This applies to data-driven processes, multiple parallel workflows, larger in­teg­ra­tions or setups that run con­tinu­ously. In these en­vir­on­ments, many processes may run at the same time, and short load spikes are common. Strong CPU per­form­ance, plenty of RAM and generous storage help keep the system stable as your workflows grow.

An overview of setup re­com­mend­a­tions

Use case Re­com­men­ded setup Typical usage
Personal use / light­weight auto­ma­tions 2–4 vCores CPU, 4 GB RAM, 80–120 GB NVMe In­di­vidu­al workflows, social media auto­ma­tions, email no­ti­fic­a­tions, small API in­teg­ra­tions
Startups / regular auto­ma­tions 4 vCores CPU, 4–8 GB RAM, 120 GB NVMe Lead pro­cessing, CRM sync, marketing auto­ma­tions, multiple parallel workflows
Business workflows / regular daily use 6 vCores CPU, 8 GB RAM, 240 GB NVMe Business processes, data in­teg­ra­tions between tools, recurring workflows used by several team members
High-volume workflows / heavier workloads 8+ vCores CPU, 16 GB RAM, 320+ GB NVMe Many parallel workflows, data-heavy processes, API-heavy in­teg­ra­tions, con­tinu­ous operation
n8n Hosting
The best VPS+ for more pro­ductiv­ity with n8n auto­ma­tion
  • Automates manual routines for tech teams
  • Over 500 in­teg­ra­tions and tools with open source
  • Auto­ma­tion on your own server with no task limits and full cost control

Step 2: Install CasaOS

Before you install n8n, you need CasaOS as the man­age­ment interface. CasaOS lets you install and manage ap­plic­a­tions like n8n in just a few clicks, so you do not need to work directly with Docker or complex server commands for every step.

First, connect to your server. This is usually done with SSH. Open a terminal and enter the following command:

ssh root@YOUR-SERVER-IP
bash

Replace YOUR-SERVER-IP with your server’s actual IP address. Then confirm the con­nec­tion and enter your password.

Note

If you don’t have direct root access, log in with a regular user account and run ad­min­is­trat­ive commands with sudo.

Once you’re connected to your server, install CasaOS with this command:

curl -fsSL https://get.casaos.io | sudo bash
bash

This downloads the official in­stall­a­tion script and runs it auto­mat­ic­ally. CasaOS installs and con­fig­ures the required com­pon­ents for you. You’ll see several status messages in the terminal while the setup runs. It’ll usually take just a few minutes.

Image: Install CasaOS
In­stalling CasaOS only takes a few minutes.

After in­stall­a­tion, open your browser. Enter your server’s IP address in the address bar to open CasaOS:

http://YOUR-SERVER-IP
Tip

If CasaOS or n8n won’t open in the browser, your firewall may be blocking access. Check your server’s firewall settings and allow the needed port, such as port 80 for CasaOS or port 5678 for n8n. After that, try opening the page again.

Step 3: Log in to CasaOS and fa­mil­i­ar­ise yourself with the interface

After you enter the server IP address your browser, the CasaOS interface will open. The first time you access it, CasaOS will guide you through setup. Create a user, set a secure password and log in. After logging in, you’ll see the main CasaOS dashboard. The interface’s design is de­lib­er­ately kept simple, so you can find your way around quickly even if you’ve never used it before.

The main areas are:

  • App Store: Install new ap­plic­a­tions like n8n in a few clicks
  • Installed Apps: View and manage the apps already running on your server
  • System overview: Check server load, including CPU, memory and storage usage

From the dashboard, you can check your server status and manage your installed apps in one place.

Image: CasaOS interface
CasaOS’s is simple in design and easy to use.

Step 4: Install n8n through the App Store

After you’ve logged in to CasaOS, you can install n8n directly via the interface. Open the App Store from the CasaOS dashboard and enter ‘n8n’ in the search bar. When n8n appears in the search results, click the app.

Image: Search for n8n in the CasaOS App Store
Search for n8n in the CasaOS App Store and install it in one click.

CasaOS will open the n8n setup page. Click Install to start the in­stall­a­tion.

Image: n8n setup settings
CasaOS will you show the n8n setup settings before in­stall­a­tion. Most fields, however, are already filled in.

CasaOS now takes care of in­stalling n8n with Docker for you. It downloads the Docker image, creates the Docker container and applies the basic settings auto­mat­ic­ally. After a short time, you’ll see n8n in your installed apps. Use the n8n tile in CasaOS to start the app and open the n8n interface.

Tip

There are other ways to install n8n besides CasaOS. For more workflows, users or webhook traffic, you may prefer to install n8n on Kuber­netes. You can also set up n8n with CapRover or install it on Plesk if you already use one of those platforms.

Al­tern­at­ive: Install n8n manually with Docker as a custom app

If n8n does not appear in the App Store or if you want more control over the setup, you can add it as a custom app. Open the App Store and click Custom Install or + Add App (depending on your CasaOS version). Then select the option to add an app using a Docker con­fig­ur­a­tion (Compose / YAML). CasaOS will open a setup screen where you can add your Docker con­fig­ur­a­tion. Paste in this code:

services: 
  n8n: 
    image: docker.n8n.io/n8nio/n8n 
    restart: unless-stopped 
    ports: 
      - "5678:5678" 
    environment: 
      - N8N_HOST=n8n.yourdomain.co.uk
      - N8N_PORT=5678 
      - N8N_PROTOCOL=http 
    volumes: 
      - n8n_data:/home/node/.n8n 
 
volumes: 
  n8n_data:
yaml

This con­fig­ur­a­tion ensures n8n starts as a container, opens the default port 5678 and stores your n8n data in a per­sist­ent volume. After you paste the code, save the custom app and start the in­stall­a­tion.

CasaOS will create the container and add n8n to your app overview. After a few moments, n8n is ready to use.

Note

This setup is enough for initial testing. If you want to use n8n regularly, you should also set up a domain, enable HTTPS and configure the correct webhook URL. Step 6 explains how to do this.

Step 5: Start n8n and open the interface

Once the in­stall­a­tion is complete, go to the Installed Apps in the dashboard. There you’ll see all the apps that are currently installed on your server. Find n8n in the list. In most cases, it is already running after in­stall­a­tion. If it is not, start it from the CasaOS interface and then open the app.

Image: Launch the n8n app
n8n now appears in your installed apps. Click on the tile to start it

When n8n is running, open it in your browser with this address:

http://YOUR-SERVER-IP:5678

Replace YOUR-SERVER-IP with your server’s actual IP address. Port 5678 is the default port for n8n, so make sure to include it.

If everything has been set up correctly, the n8n interface will open. The first time you open it, you’ll usually see the n8n editor or a short setup page. From there, you can create your first workflow.

Step 6: Prepare n8n for everyday use

After in­stalling and opening n8n in CasaOS, it’s worth adjusting a few settings before you start using it regularly. This is es­pe­cially important if n8n needs to be ac­cess­ible from outside your local setup. Con­fig­ur­ing it correctly first helps avoid issues with webhooks, external access and security later.

Set up a domain or subdomain

By default, n8n is available through your server’s IP address over an un­en­cryp­ted HTTP con­nec­tion. That is fine for initial testing, but it is not ideal for everyday use. Instead, you should access n8n through a fixed domain and secure the con­nec­tion with HTTPS. HTTPS encrypts the con­nec­tion, prevents browser security warnings and helps webhooks work more reliably.

Start by creating your own domain or subdomain like n8n.yourdomain.co.uk. Then point it to your server’s IP address with a DNS record usually an (A record). Once the DNS record is active, you can open n8n through your domain instead of entering the server IP address.

Set up a reverse proxy

You’ll also need a reverse proxy so the domain works with n8n. A reverse proxy receives requests for your domain and forwards them to the n8n port on your server. nginx and Caddy are two solid options. A reverse proxy can also handle HTTPS cer­ti­fic­ates for you.

For en­cryp­tion, you can use Let’s Encrypt. This free service issues valid SSL cer­ti­fic­ates and renews them auto­mat­ic­ally. Many reverse proxies support Let’s Encrypt directly, so setting up HTTPS is usually straight­for­ward.

Set en­vir­on­ment variables

You should also set a few en­vir­on­ment variables so n8n knows which public address to use and how to create webhook URLs. A typical con­fig­ur­a­tion is as follows:

N8N_HOST=n8n.yourdomain.co.uk
N8N_PROTOCOL=https 
WEBHOOK_URL=https://n8n.yourdomain.co.uk/ 
N8N_PROXY_HOPS=1

These values tell n8n that is available through your domain over HTTPS. In CasaOS, you can add them in the n8n app settings. To do this, open Installed Apps, select n8n, and enter the values in the en­vir­on­ment variables section. Then save the changes and restart the container so the new settings apply.

If you plan to use n8n regularly, you should also set N8N_ENCRYPTION_KEY. n8n uses this key to encrypt sensitive data, including login cre­den­tials and API keys. If you do not set your own key, n8n will generate one auto­mat­ic­ally. A fixed key is safer for self-hosted setups because it keeps cre­den­tial handling con­sist­ent if the container changes later.

Reviewer

Go to Main Menu