Your First n8n Workflow – Lab Guide

Installation (Docker)

If you prefer to run n8n locally with Docker, follow these steps:

Create a Docker volume to persist n8n data:
docker volume create n8n_data
Run n8n in a container:
docker run -it --rm --name n8n -p 5678:5678 -e GENERIC_TIMEZONE="America/New_York" -e TZ="America/New_York" -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true -e N8N_RUNNERS_ENABLED=true -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n

n8n will be available at http://localhost:5678. The -it --rm flags run the container interactively and remove it when stopped; remove them if you want the container to run in the background.

1. Prerequisites

Before starting, make sure you have access to n8n. You can use:

This lab uses the HTTP Request node with JSONPlaceholder, a free fake REST API that requires no API keys or authentication.

2. Create a New Workflow

Click the "+" button in the left sidebar at the top, then select Workflow to create a new workflow.
You will see an empty workflow editor with a canvas. The canvas is where you add and connect nodes to build your automation.

3. Add the Manual Trigger

On the right side of the canvas, click the + button to open the node search panel.
In the search box, type Manual trigger and select it from the results.
The Manual Trigger node appears on the canvas. This node starts your workflow when you click Execute Workflow (useful for testing and demos).

4. Add the HTTP Request Node

Click the + button that appears next to the Manual Trigger node (or on the canvas connection point).
In the search box, type http and select HTTP Request from the results.
n8n adds the HTTP Request node to your canvas and automatically connects it to the Manual Trigger. The node configuration panel opens on the right.

5. Configure the HTTP Request

In the node configuration panel, set Method to GET.
In the URL field, enter:
https://jsonplaceholder.typicode.com/posts
This endpoint returns 100 fake blog posts. No authentication is required.
Click Execute Step (or the play button on the HTTP Request node). n8n will make the request and display the JSON response in the output panel on the right.
Review the output. You should see an array of posts, each with userId, id, title, and body.
Click the close (×) button on the node configuration panel to return to the canvas view.

6. Execute the Full Workflow

Click Execute Workflow button at the bottom. This runs the entire workflow from the Manual Trigger through the HTTP Request node.
Both nodes should show a green checkmark when execution completes successfully. Click on either node to view its output.

7. Save Your Workflow

Click Save (or press Ctrl+S / Cmd+S) in the top-right corner.
Give your workflow a meaningful name (e.g., First Workflow – Fetch Posts) and add an optional description.

8. Understanding the Output

The HTTP Request node returns data as items. Each item is a JSON object. For the /posts endpoint:

In later workflows, you can reference these fields using expressions like {{ $json.title }} or {{ $json.body }}.

9. Add a Second Node

Your Task

Add an Edit Fields (Set) node after the HTTP Request to transform the data:

  1. Click the + after the HTTP Request node.
  2. Search for Edit Fields or Set and add it.
  3. In the Set node, add a field: summary = {{ $json.title }} (to keep only the title as a summary).
  4. Execute the workflow and compare the output before and after the Set node.