Skip to content

Lesson 11 – n8n Workflow Automation

n8n is an open-source workflow automation tool that lets you connect services with low-code building blocks. This lesson covers installation, core node types, and how to design practical flows.


1. Getting Started with n8n

  1. Install using one of the following methods:
  2. npx n8n for a quick local run.
  3. Docker: docker run -it --rm -p 5678:5678 n8nio/n8n.
  4. Open http://localhost:5678 in your browser to access the editor.
  5. Create an account and explore the canvas where workflows are built.

2. Understanding Nodes

Nodes are the building blocks of n8n. They come in two categories:

  • Trigger Nodes: start a workflow (e.g., Webhook, Cron, Schedule).
  • Regular Nodes: perform actions like HTTP requests, data transforms, or sending messages.

Common nodes you will use:

  • HTTP Request – fetch data from APIs.
  • Set – define or restructure fields.
  • Function – add custom JavaScript logic.
  • Slack – send notifications to a channel.

3. Sample Workflow

The following flow listens for a Webhook, calls an API, formats the response, and posts to Slack.

graph LR
    A[Webhook Trigger] --> B[HTTP Request]
    B --> C[Set Node]
    C --> D[Slack Node]

The Mermaid source is available at n8n_sample_flow.mmd.


4. Practical Tips

  • Use the Expression Editor to reference data from previous nodes: {{$json["field"]}}.
  • Store credentials securely using environment variables or the built-in credential manager.
  • Enable Execution Data to debug and review past runs.

5. Next Steps

  • Explore community nodes to integrate with more services.
  • Chain multiple workflows using the Execute Workflow node.
  • Deploy n8n on a server or cloud provider for always-on automations.

Automating workflows with n8n bridges user interfaces and services with low-code flexibility. Building on Lesson 10 – Gemini Canvas UI Design's reminder that natural-language prompts can yield functional components, your learning path now moves to Module 03's Lesson 01 – Agile Kanban, where you'll begin applying Agile QA practices.