> ## Content Index
> Fetch the complete content index at: https://linuxhandbook.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Chapter 2: Basics of n8n
- URL: https://linuxhandbook.com/courses/n8n/n8n-basics/
- Published: 2026-11-20T14:20:46.000Z
- Updated: 2026-11-20T14:20:46.000Z
- Author: Yash Kiran Patil
- Tags: n8n, #lessons-col, #lesson-duration-20m

As we defined in the introduction, an automation is a sequence of tasks arranged so that one follows another. A workflow makes sure those tasks are executed in the order and conditions we define.

In this chapter, we’ll explain what n8n is, how to install it on your Linux computer, and how to recognize the basic parts of its web interface before creating workflows.

## How to get n8n

There are several ways to run n8n. You can install it locally with npm or Docker, use n8n Cloud, or host it on a server you manage. n8n is a TypeScript web application. Its source code is available under the Sustainable Use License, which n8n describes as fair-code. The Community edition can be used without a software subscription for permitted personal or internal use; review the [license FAQ](https://support.n8n.io/article/can-i-use-your-license-for-my-use-case?ref=linuxhandbook.com) for commercial limits and edge cases.

## Install n8n locally

For a first experiment, you can run n8n on your own computer. The two local options covered here are npm and Docker. npm runs n8n with Node.js installed on your system. Docker runs it in a container, which keeps the application environment separate and makes the same image available on different systems.

### Install with npm

n8n’s current npm installation guide supports Node.js versions 20.19 through 24.x. Install a supported Node.js version and npm for your Linux distribution. A version manager such as nvm is useful if you need to switch Node.js versions. Check your installation from a terminal:

```
node --version
npm --version
```

When Node.js and npm are ready, install n8n globally:

```
npm install n8n -g
```

You can check which version was installed with:

```
n8n --version
```

Start n8n from the command line:

```
n8n
```

Leave that terminal running and open [http://localhost:5678](http://localhost:5678/?ref=linuxhandbook.com) in your browser. n8n is a web application started from the terminal; it does not add an application menu icon. See the [official npm installation guide](https://docs.n8n.io/hosting/installation/npm/?ref=linuxhandbook.com) for supported versions and current instructions.

### Install with Docker

First, make sure Docker is installed and running. You can check its version with:

```
docker --version
```

Download the n8n image:

```
docker pull n8nio/n8n
```

Docker images are the packaged application used to start containers. Next, create a named volume for n8n’s data:

```
docker volume create n8n_vol
```

The volume keeps the data outside the container’s writable layer. A container restart does not by itself erase data. Without a volume, data in the container’s writable layer is lost if that container is removed and recreated. A named volume can be reused by a replacement container and remains until you remove the volume itself.

Now start the container. This example binds the web interface to your own machine, uses the same image name that was pulled above, sets the time zone, and enables restrictive permissions for the settings file. Replace `Asia/Kolkata` with your local IANA time-zone name if necessary.

```
docker run -d \
  --name n8n \
  -p 127.0.0.1:5678:5678 \
  -v n8n_vol:/home/node/.n8n \
  -e N8N_HOST=localhost \
  -e N8N_PORT=5678 \
  -e N8N_PROTOCOL=http \
  -e GENERIC_TIMEZONE="Asia/Kolkata" \
  -e TZ="Asia/Kolkata" \
  -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \
  n8nio/n8n
```

The `docker run` command creates and starts the container. The `-d` option runs it in the background, so the terminal returns to the prompt. The `--name` option gives the container a convenient name. The port mapping makes n8n available at port 5678 on your computer, and the `-v` option mounts the persistent volume at n8n’s data directory inside the container.

Each `-e` option sets an environment variable in the container. Here, the host, port, and protocol describe the local address; `GENERIC_TIMEZONE` and `TZ` set the time zone used for scheduled workflows and the container; and `N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true` tells n8n to enforce restrictive permissions on its settings file. The final argument, `n8nio/n8n`, is the image used to create the container.

Open [http://localhost:5678](http://localhost:5678/?ref=linuxhandbook.com) in your browser and complete the initial owner account setup. To stop and start the container later, run `docker stop n8n` and `docker start n8n`. Keep the named volume and use it when recreating the container if you want to keep your workflows and credentials. Back up the volume before maintenance. This local example is for learning; do not expose an instance directly to the public internet without following n8n’s [hosting and security guidance](https://docs.n8n.io/hosting/?ref=linuxhandbook.com).

Is there a difference between running n8n on your own computer and using another hosting option? This illustration compares a local installation with hosted n8n:

![Diagram comparing a local n8n setup on a computer with a hosted n8n instance and summarizing their trade-offs](https://linuxhandbook.com/content/images/2026/11/image87-1.png)

Using n8n locally is useful for experimenting and learning the components. Your computer must remain on and n8n must be running for workflows to execute. If your computer is off or disconnected, scheduled workflows stop until the service is available again. A local computer is convenient for learning, while a server or managed Cloud service is more suitable when a workflow must be available continuously.

## Host n8n online

If you need workflows to run while your personal computer is off, you can use n8n Cloud or host n8n on a server. With n8n Cloud, n8n operates the service and you manage your workflows through a browser. With self-hosting, you choose and maintain the server and are responsible for updates, backups, security, and availability.

n8n Cloud has subscription plans and execution limits. Prices, trials, and plan features can change, so check the [current pricing page](https://n8n.io/pricing/?ref=linuxhandbook.com) before choosing. Self-hosting may avoid an n8n software subscription for permitted uses, but the server, electricity, backups, AI APIs, and connected services can still cost money.

You can opt for [n8n hosting with PikaPods](https://www.pikapods.com/apps/n8n?ref=linuxhandbook.com). It is cost effective and you should be able to control your n8n deployment with env vars.

[Managed n8n Hosting from $3.75/Month | PikaPodsHost n8n workflow automation from $3.75/month on PikaPods. Connect apps, build visual workflows and automate tasks familiar to Zapier users.![](https://linuxhandbook.com/content/images/icon/favicon-958ce4ad-c910-45b2-910f-9b3d96ac2921.png)PikaPods![](https://linuxhandbook.com/content/images/thumbnail/og_image-v2-8f91567d-0dd8-4a6e-bf25-ac31f489871a.jpg)](https://www.pikapods.com/apps/n8n?ref=linuxhandbook.com)

## Explore the n8n interface

After you sign in for the first time, n8n opens an overview of the workspace. This screenshot from the manuscript points out the main areas of the interface:

![](https://linuxhandbook.com/content/images/2026/11/image26-2.png)

The overview presents information about workflows and their executions. The navigation gives you access to workflows and other areas of the workspace. The exact labels, available sections, and metrics can change between n8n versions and plans, so treat the screenshot as a guide to the layout rather than a promise that every account will look exactly the same.

Templates can help you start from an existing workflow instead of building every node from scratch. Settings contain instance or account options, depending on how n8n is hosted. Help links provide documentation and support. Some administrative and analytics areas depend on the hosting setup or plan.

The next step is to open the workflow editor. In the manuscript’s example, selecting *Create Workflow* opens a blank workflow like this:

![](https://linuxhandbook.com/content/images/2026/11/image114-1.png)

This is the canvas where you’ll spend most of your time designing a workflow. Before adding nodes, give the workflow a clear name so you can identify its purpose later. The screenshot highlights the workflow name:

![](https://linuxhandbook.com/content/images/2026/11/image93-1.png)

n8n may start with a generated name such as “Workflow 1.” Replace it with a descriptive name that explains what the automation does. “Email Automation” or “Video Creation” is easier to recognize than a generic number. The interface shown in the screenshot may differ slightly from your version.

The canvas is the central area where you arrange nodes and connect them. A new workflow begins without any nodes:

![](https://linuxhandbook.com/content/images/2026/11/image40-2.png)

To begin, choose the first step. The example screenshot points to the *Add the first step* control:

![](https://linuxhandbook.com/content/images/2026/11/image106-1.png)

The side panel also has a plus button for adding or searching for nodes and applications. You’ll use it to add triggers and actions as you build. Button locations and labels may change between versions.

## Summary

In this chapter, we introduced n8n, compared ways to run it, installed it locally with npm and Docker, and looked at the main parts of the web interface. This final illustration recaps the areas described above:

![Infographic summarizing the n8n interface, workspace overview, workflow canvas, controls, and node panel](https://linuxhandbook.com/content/images/2026/11/image33-1.png)

For now, remember how to start n8n, open or create a workflow, rename it clearly, and find the canvas and node controls.

 In the next chapter, we’ll work on the canvas as we build our first workflow.