Introduction

n8n's editor is where you spend most of your time — building, testing, and debugging automation workflows. Before writing any logic, you need to feel at home in the interface. This lesson walks you through every major area of the editor and introduces the three building blocks that every n8n workflow is made of: workflows, nodes, and connections.

The Editor Interface

When you open n8n and create a new workflow, you land in the canvas — a blank grid where you drag, drop, and wire things together. The interface has a few key areas to know.

The top bar holds the workflow name (click it to rename), the Save button, and the Execute Workflow button, which runs the entire workflow manually. On the far right you have access to workflow settings and your account menu.

The left sidebar is your node panel. Click the plus icon or press Tab to open it. From here you search for and add nodes to the canvas. Nodes are grouped by category: trigger nodes (the starting points), action nodes (things that do work), and utility nodes (data transformation helpers).

The canvas itself supports a few navigation shortcuts worth learning early. Scroll to zoom in and out. Hold Space and drag to pan. Press Ctrl+Shift+F (or Cmd+Shift+F on Mac) to fit the entire workflow into view.

Workflows, Nodes, and Connections

Every automation in n8n is a workflow — a saved document that contains a graph of nodes wired together. A workflow can be active (runs automatically when triggered) or inactive (only runs when you manually execute it).

A node is a single unit of work. Each node has a specific job: fetch data from an API, transform a value, send an email, insert a row into a database. Nodes are the verbs of your automation. When you double-click a node, its parameter panel opens on the right side, where you configure what it does.

Nodes come in two flavors. Trigger nodes start a workflow — they listen for an event (a webhook call, a schedule, a new row in a sheet) and fire when that event happens. Every workflow needs exactly one trigger node, and it always sits on the left. Regular nodes do the actual work and chain off the trigger.

Connections are the arrows between nodes. They carry data from one node to the next. To draw a connection, hover over the right edge of a node until you see a circle, then drag to the input handle of the next node. Data flows left to right.

Working with Node Data

n8n passes data between nodes as an array of items. Each item is a JSON object. When a node executes, it receives items from the previous node, processes them, and outputs new items to the next node.

To see what data a node produced, click it after a test run. The output panel shows each item as a formatted JSON object. This is your primary debugging tool — you inspect the output of each node to verify the data looks correct before building the next step.

Here is what a typical item looks like in the output panel:

{
  "id": 42,
  "name": "Alice",
  "email": "alice@example.com",
  "createdAt": "2024-01-15T10:30:00Z"
}

To reference a value from a previous node inside a parameter field, n8n uses expressions. You switch a field from static text to an expression by clicking the expression toggle (the small equals sign icon next to the field). Inside an expression you use the syntax below to pull a value:

{{ $json.email }}

This pulls the email field from the current item's JSON. You will use this pattern constantly — it is the primary way nodes talk to each other.

Saving and Executing

Always save your workflow before executing. Press Ctrl+S (or Cmd+S) or click the Save button. Unsaved changes are shown with a dot next to the workflow name.

To test a workflow, click Execute Workflow in the top bar. n8n runs every node from the trigger onward and shows a green checkmark on each node that succeeded or a red error badge on any that failed. Click a failed node to read the error message in its output panel.

For trigger nodes that wait for external events (like a Webhook node), n8n has a Test mode. Click Listen for Test Event on the Webhook node, then fire the request from your external system. n8n captures one real payload and lets you build and test the rest of the workflow against that data without waiting for another real event.

Summary

The n8n editor is built around one canvas, a library of nodes, and the connections between them. Workflows hold your automation logic. Trigger nodes start execution. Regular nodes process data. Connections carry JSON items from left to right. The output panel after each test run is how you verify everything is working. Get comfortable clicking around, adding nodes, and inspecting outputs — the rest of the course builds directly on these mechanics.