Your First n8n Workflow – Lab Guide
Installation (Docker)
If you prefer to run n8n locally with Docker, follow these steps:
docker volume create n8n_data
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:
- n8n Cloud – Sign up at n8n.io for a free account.
- Self-hosted – Run
npx n8nin a terminal to start n8n locally (default:http://localhost:5678).
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
3. Add the Manual Trigger
4. Add the HTTP Request Node
5. Configure the HTTP Request
https://jsonplaceholder.typicode.com/posts
This endpoint returns 100 fake blog posts. No authentication is required.
userId, id, title, and body.
6. Execute the Full Workflow
7. Save Your Workflow
8. Understanding the Output
The HTTP Request node returns data as items. Each item is a JSON object. For the /posts endpoint:
- 100 items – one for each post in the response array.
- Each item has:
userId,id,title,body.
In later workflows, you can reference these fields using expressions like {{ $json.title }} or {{ $json.body }}.
9. Add a Second Node
Add an Edit Fields (Set) node after the HTTP Request to transform the data:
- Click the + after the HTTP Request node.
- Search for Edit Fields or Set and add it.
- In the Set node, add a field:
summary={{ $json.title }}(to keep only the title as a summary). - Execute the workflow and compare the output before and after the Set node.