Learn n8n - Pre-Requisite Skills & Environment Setup

#Introduction

Welcome to the Learn n8n series! This series will take you to mastering n8n — an open-source platform for workflow automation with a visual editor and hundreds of ready-to-use integrations — from the conceptual foundations all the way to production-grade deployment across 23 episodes.

Before building your first workflow, there are several basic skills and tools you need to prepare. Why are prerequisites important? Because n8n works at the intersection of APIs, events, and structured data — you'll constantly be dealing with JSON, webhooks, credentials, and expressions. Without this foundation, n8n nodes will feel like black boxes.

Episode 0 lays your groundwork: sharpening your understanding of API and HTTP basics, getting familiar with JSON and YAML, understanding the concept of credentials, then making sure your local environment is ready with Node.js, Docker, and a running n8n instance.

#Basic Skills You Need

#API, HTTP, and Webhook Basics

n8n is a bridge between APIs. Almost everything you automate — Slack, GitHub, databases, or internal services — communicates over HTTP with requests and responses. Three things you must understand from the start:

Webhook is the concept used most often in this series. Here's an analogy: a webhook is like a phone number that other systems call to let you know something happened. An online store calls your n8n endpoint every time a new order comes in, and n8n immediately runs the workflow.

#Getting Familiar with JSON and YAML

Most of the data flowing through n8n nodes is in JSON form. The ability to read and guess JSON structure — objects, arrays, keys, and values — will be used in almost every node:

{
  "event": "order.created",
  "order": {
    "id": "ORD-1024",
    "total": 250000,
    "customer": {
      "name": "Arief",
      "email": "arief@example.com"
    }
  }
}

The structure above is a nested object — the order object contains the customer object. You'll often access this kind of nested data through n8n expressions, so get used to reading the indentation. Meanwhile, YAML is widely used for configuration — including the docker-compose.yml file you'll use in the installation episode. YAML is more concise than JSON because it uses indentation instead of curly braces.

#Credentials, Authentication, and Secrets

n8n integration nodes need permission to call third-party APIs. Three concepts you should be familiar with from the start:

1. API key — a simple token sent in the request header for identification.
2. OAuth 2.0 — the standard authentication flow for most modern services, including Google and Slack.
3. Secret — sensitive values such as tokens and passwords that must never be hardcoded or leak into Git.

A habit you should build from now on: store secrets only in safe places. n8n provides an encrypted credential store, and for self-hosting you'll use environment variables. We'll break down the practical details in the installation and security episodes.

#Tools to Prepare

#Node.js and Docker

n8n runs on Node.js. To run n8n directly from npm, you need at least Node.js version 20 or higher. First check the version in your terminal:

node -v
npm -v

Docker is optional but highly recommended — Docker makes n8n installation clean, consistent, and easy to move around. Docker also prepares you for the deployment episodes at the end of the series. Verify with docker --version; if it's not installed yet, install it from the official Docker website according to your OS.

#n8n Desktop or Self-Hosted Instance

There are three common ways to run n8n that we'll cover thoroughly in episode 3:

• n8n desktop app — a one-click local application, the fastest way to try it out.
• Self-hosted instance — you run it yourself via Docker or Node.js, with full control over your data.
• n8n Cloud — a SaaS managed by the n8n team, with no maintenance overhead.

For the early episodes, the fastest way is via npx:

npx n8n@latest start

Once the command above runs, n8n will serve at http://localhost:5678 — your browser will open and greet you with the initial setup page. Save this address, because it will be used throughout the series.

#Text Editor and Browser

n8n is a web application, so a modern browser (Chrome, Firefox, or Edge) is a must for its visual editor. It's best to open it in a separate browser window so it doesn't get buried under other tabs.

In addition, prepare a text editor — for example VS Code, Neovim, or Zed — to work with configuration files, exported JSON workflows, and small scripts outside of n8n. Throughout the series you'll frequently copy JSON structures between files, so a comfortable editor goes a long way.

#Verifying Your Environment

Let's make sure everything is ready. Run these three checks in order:

node -v
docker --version
npx n8n@latest --version

If node -v shows version 20 or higher, docker --version shows a Docker version, and npx n8n@latest --version shows the n8n version number, then your environment is officially ready. Don't worry if Docker isn't installed yet — all the examples in the early episodes still work with npx or the desktop app alone.

#Closing

In episode 0 you've prepared the foundation for the entire series: a basic understanding of APIs, HTTP, webhooks, JSON, YAML, the concept of credentials, as well as a local environment with Node.js, Docker, and an n8n instance ready to run.

Key takeaways:

• n8n is a bridge between APIs — master HTTP methods, status codes, and the webhook concept.
• The ability to read JSON and write YAML is a daily skill when building workflows.
• Secrets such as API keys and tokens should only be stored in the credential store or environment variables.
• Node.js version 20 or higher, Docker, and a modern browser are the minimum toolkit.
• n8n first serves at http://localhost:5678 via the npx n8n@latest start command.

In the next episode, we'll discuss the history, background, and why to choose n8n — how n8n was born from a project called nodemation, its position in the automation ecosystem, a direct comparison with Zapier, Make, and Huginn, and the open-source and self-hosted control advantages that lead many teams to choose it. Make sure your environment is ready, because the Learn n8n journey is just getting started!