Skip to main content
Create your own
Lesson illustration

Introduction to n8n: Automation Landscape

Hello! Welcome to your first lesson in our n8n course. Over the next month, we'll work together to build your expertise from the ground up, moving from fundamental concepts to deploying complex, AI-powered automations on your own infrastructure.

Today, we'll start by establishing a solid conceptual foundation. The goal of this lesson is to answer two key questions: "What is n8n?" and "Where does it fit in the broader landscape of automation tools?" Understanding the core philosophy and strategic advantages of n8n, especially compared to alternatives like Zapier and Make, will be crucial for making smart architectural decisions as you start building your own workflows.

Let's begin by defining what n8n is.

What is n8n?

At its heart, n8n (pronounced "en-eight-en") is a workflow automation tool. Its purpose is to connect different applications and services to automate repetitive tasks.

To understand its core architecture, let's review a brief article.

n8n: The workflow automation tool for the AI age

This article from the WorkOS blog provides a concise and clear definition of n8n and its foundational concepts.

Please read the sections 'What is n8n?' and 'Core concepts and architecture'. Start with the platform definition, paying attention to the description of n8n as a Node.js-based, open-source, and self-hostable platform. Then, review the core architecture.

As you just read, n8n is:

  • Node-based: You build automations (called "workflows") by connecting individual "nodes" on a visual canvas. Each node represents a step, such as a trigger (e.g., "when a new email arrives") or an action (e.g., "add a row to a spreadsheet"). Data flows from one node to the next.
  • Event-driven: Workflows can be initiated by specific events (like a webhook call), run on a schedule, or be triggered manually.
  • Source-available & Self-hostable: This is a major differentiator. You can access the source code and run n8n on your own servers. This gives you complete control over your data, security, and infrastructure, which directly aligns with your goal of managing your own self-hosted instance.
  • Developer-friendly: Built on Node.js, it's designed for extensibility. As a software developer, you'll find the ability to write custom JavaScript code directly within nodes invaluable for handling complex logic.

The image below highlights three of n8n's most powerful features, which directly correspond to your learning goals.

This image showcases three key differentiating features of n8n: the ability to self-host for data control, the option to integrate custom code for advanced logic, and built-in capabilities for connecting with AI services.

n8n's Position in the Automation Landscape

To truly understand n8n, it's best to compare it to the other major players in the field: Zapier and Make (formerly Integromat). While all three tools automate tasks, they are optimized for different users and priorities.

Think of the landscape as a spectrum:

  • On one end, you have Zapier, which prioritizes ease of use and has the largest number of pre-built app integrations. It's excellent for non-technical users and simple, linear automations.
  • In the middle is Make, which offers a more visual and flexible canvas than Zapier, allowing for more complex branching logic at a generally lower price point.
  • On the other end, you have n8n, which prioritizes power, flexibility, and control, making it the strongest choice for developers and technical teams.

This comparison table provides an excellent at-a-glance overview of their differences.

Zapier vs Make vs n8n - Which Automation Tool Is Best?

This article from Parseur features a fantastic comparison table and a detailed breakdown of n8n's unique characteristics.

First, study the 'Zapier vs Make vs n8n: Comparison Table' by reviewing the feature breakdown. Then, read the section 'n8n: Features, Strengths, and Limitations' to explore n8n's overview. This will give you a solid understanding of n8n's core value proposition.

Let's break down the key differentiators that are most relevant to you.

1. Hosting, Ownership, and Security

This is perhaps the most significant difference. Zapier and Make are exclusively cloud-based SaaS (Software as a Service) products. You use their infrastructure, and your data is processed on their servers.

n8n offers both a managed cloud version and a self-hostable version. For your goal of mastering the "full stack" of n8n, the self-hosting capability is paramount. It means you can:

  • Deploy n8n within your own private cloud or on-premise servers.
  • Ensure full data privacy and compliance with regulations like GDPR or HIPAA.
  • Have complete control over security, maintenance, and scaling.

The video below gives a great summary of these high-level trade-offs, including security.

n8n vs Zapier | We Compared Everything

To hear these concepts explained, watch the concluding summary from this comparison video by Futurepedia. It clearly articulates the trade-offs across several key dimensions.

About 15 minutes into the video, watch the summary. Focus on the four points of comparison: ease of use, integrations, capabilities, and security/operations.

2. Flexibility and Extensibility

Where Zapier guides you through a linear, form-based setup, n8n gives you a canvas and exposes the underlying data structures.

This diagram compares the core terminology and workflow structure of Zapier (Zaps with Steps), n8n (Workflows with Nodes), and Make.com (Scenarios with Modules). Note n8n's concepts like Switches and IF nodes, which point to its built-in capacity for complex logic.

In n8n, data is passed between nodes as JSON objects. You have direct access to inspect and manipulate this JSON at every step, often using JavaScript expressions. For a developer, this transparency is a massive advantage. Rather than being constrained by a simplified interface, you can implement custom transformations and complex logic with precision.

The ultimate form of this extensibility is the Code node, which allows you to write arbitrary JavaScript to perform tasks that aren't possible with pre-built nodes.

3. Pricing and Scalability

The pricing models also reflect their different philosophies.

  • Zapier and Make primarily charge per task or operation. Every action a workflow performs often counts against your monthly quota. A workflow with 10 steps could use 10 operations each time it runs.
  • n8n's cloud plans charge per workflow execution. A workflow with 10 steps still only counts as one execution.
  • Self-hosted n8n is free to use (under its fair-code license). Your only cost is the infrastructure you run it on.

This distinction is critical for complex or high-volume workflows. An automation that processes thousands of items could become prohibitively expensive on an operation-based model but remain highly cost-effective on n8n.

This video provides an excellent breakdown of the different pricing models.

Zapier vs Make.com vs n8n: The Ultimate 2025 Beginners Guide

The pricing model is a crucial factor for scalability. This video details the different approaches taken by each platform.

Starting less than a minute into the video, watch the pricing section. Focus on the difference between operation-based pricing and workflow execution-based pricing, and the implications of the free, self-hosted Community Edition.

Test your understanding!

You need to build a workflow that listens for new customer sign-ups. For each sign-up, it needs to:

  1. Check if the customer's email domain exists in a company database.
  2. Enrich the customer's profile with data from a third-party API like Clearbit.
  3. Based on their industry, add them to a specific mailing list in Mailchimp.
  4. Send a customized welcome message to a specific Slack channel.

Why might n8n be a more suitable and scalable choice for this workflow compared to an entry-level plan on Zapier?

Show answer

There are two main reasons:

  1. Complexity: The workflow involves conditional logic ("if domain exists") and data enrichment, which is more naturally handled in n8n's node-based canvas where you can easily branch, merge, and transform the JSON data at each step.
  2. Cost at Scale: This workflow involves at least 4-5 steps (Trigger, DB Check, API Call, Add to List, Slack Message). On an operation-based platform like Zapier, this would consume 4-5 tasks per customer. If you have hundreds or thousands of sign-ups, the cost would scale linearly. On a self-hosted n8n instance, the software cost would be zero, regardless of the number of sign-ups or workflow steps.

Conclusion: Why Choose n8n?

You should choose n8n when your priority is control, power, and customization. It is the ideal tool for developers, technical teams, and anyone building mission-critical or complex automations.

The article from Parseur we looked at earlier has a section that perfectly summarizes the ideal use cases.

Zapier vs Make vs n8n - Which Automation Tool Is Best?

Let's conclude by revisiting the Parseur article to see its final recommendation on when to choose n8n.

Locate the section 'When to Use Zapier, Make, or n8n: Industry Examples'. Read the industry examples, focusing specifically on the use case described for n8n at the end.

Key Takeaways:

  • n8n is a source-available, self-hostable workflow automation tool that gives you maximum control over your data, infrastructure, and security.
  • It competes with tools like Zapier and Make but is positioned as a more powerful and flexible platform for developers and technical users.
  • Its key advantages are its developer-friendly extensibility (custom code, direct JSON manipulation), cost-effective scaling (execution-based pricing and free self-hosting), and unparalleled control through its self-hosting option.

You've now established a strong conceptual map of the automation landscape and n8n's unique place within it. This understanding will guide you as we move from theory to practice.

In our next lesson, we'll get our hands dirty for the first time by navigating the n8n user interface. We'll explore the canvas, the node panel, and the execution panel—the three main areas you'll use to build and debug your workflows.

Can't find a good explanation? Sign up and we'll make it for you

Sign up