What Is Workflow Automation?
Workflow automation is the practice of connecting apps, services, and data sources so that tasks move from one step to the next without manual intervention. Instead of a person copying data from a form into a spreadsheet, then sending an email, then updating a CRM — a workflow handles all of that the moment the trigger fires.
The value is not just speed. It is consistency. A workflow does the same thing every single time, at 3am on a Sunday just as reliably as at 9am on a Monday. That reliability is what makes automation worth building.
A workflow typically has three parts: a trigger (something that starts the process), one or more actions (things that happen as a result), and often some logic in between (conditions, transformations, branching). Almost every automation tool — from simple Zapier zaps to complex enterprise pipelines — follows this same pattern.
Where n8n Fits In
n8n (pronounced "n-eight-n") is an open-source workflow automation platform. It gives you a visual canvas to build workflows by connecting nodes, where each node represents a step: fetching data from an API, running a transformation, sending a message, writing to a database, and so on.
What separates n8n from tools like Zapier or Make (formerly Integromat) is the combination of two things: you can self-host it, and you can write real code inside your workflows. Those two properties matter a lot depending on your situation.
Zapier is cloud-only, fast to start, but expensive at scale and limited when you need custom logic. Make is more flexible with its visual data mapping, but still cloud-hosted and can get complex to manage at scale. n8n sits in a different position: it is free to self-host, has over 400 built-in integrations, and lets you drop into JavaScript or Python nodes whenever the visual approach is not enough.
Key Concepts You Will See Throughout This Course
Before going further, a few terms are used consistently everywhere in n8n and in this course.
A workflow is the full automation you build — the canvas with all its nodes and connections. A node is a single step in that workflow. Every node either receives data, does something with it, or passes it along. The data flowing between nodes is structured as items, and each item is a JSON object.
This JSON-based data model is important. When a webhook receives a POST request, n8n turns it into an item. When you query a database, each row becomes an item. When you call an API, the response becomes one or more items. Everything normalizes to the same shape, which makes it predictable to work with.
n8n has two main node categories: trigger nodes (they start a workflow — a schedule, a webhook, a new row in a sheet) and action/processing nodes (they do work — HTTP requests, if/else branching, data merging, sending emails, and so on).
A Concrete Example Before We Build Anything
Imagine this process: every time a new row is added to a Google Sheet, check whether the email column is filled in. If it is, send a welcome email via Gmail. If it is not, post a Slack alert to a monitoring channel.
In n8n, this is four nodes wired together.
Node 1 — Google Sheets Trigger: fires when a new row appears. Node 2 — IF node: checks whether the email field is empty. Node 3a — Gmail node: sends the welcome email (true branch). Node 3b — Slack node: posts the alert (false branch).
No server to write, no cron job to maintain. The workflow runs on its own, and if you need to change the email template you open the canvas and edit one node. That is the practical promise of workflow automation.
Summary
Workflow automation connects triggers, logic, and actions to move work forward without manual steps. n8n is an open-source platform in this space that stands out because it is self-hostable, supports custom code, and has a large library of built-in integrations. The core data model is JSON items flowing between nodes, which is a pattern you will see in every workflow you build throughout this course. The rest of this course moves from this conceptual foundation into hands-on building.
Lesson Checkpoint