n8n is an open-source workflow automation tool that connects applications and services through a visual, node-based interface. It is distinguished from comparable platforms by its flexibility: it can be self-hosted, it imposes no execution limits on a self-hosted instance, and it permits custom code where visual configuration is insufficient. This tutorial introduces the concepts required to build a first workflow with confidence.
1. Nodes: the unit of work
In n8n, every operation is performed by a node. A node represents a single action — retrieving data from an API, transforming a value, or writing to a database. A workflow is a set of nodes joined by connections, and data flows along those connections from one node to the next. Building an automation in n8n is therefore the practice of selecting the appropriate nodes and connecting them in a logical order.
2. Triggers start the workflow
Every workflow begins with a trigger node, which determines when the workflow runs. Common triggers include:
- A schedule trigger, which runs the workflow at fixed intervals.
- A webhook trigger, which runs the workflow when an external service sends a request.
- An app trigger, which responds to an event within a connected service.
Selecting the correct trigger is the first decision in designing any workflow.
3. Connecting nodes and passing data
Once a trigger is in place, action nodes are added and connected to it. Data passes between nodes as a structured list of items, and each node operates on the items it receives. Understanding this flow of items is the single most important concept in n8n: a node’s output becomes the next node’s input, and most difficulties arise from a misunderstanding of the shape of that data.
4. Expressions: working with dynamic data
Static configuration is rarely sufficient. n8n provides expressions, which allow a field to reference data from earlier nodes rather than a fixed value. An expression can extract a specific field, combine values, or apply a transformation. Mastery of expressions is what separates a rigid workflow from one that adapts to the data it processes.
A walkthrough of building a workflow from start to finish:
5. Error handling and reliability
A workflow intended for production must anticipate failure. n8n supports a dedicated error workflow that executes whenever another workflow fails, enabling immediate notification and recovery. Individual nodes can also be configured to continue on error or to retry. Designing for failure from the outset is what distinguishes a dependable automation from a fragile one.
6. Self-hosted or cloud
n8n may be run as a managed cloud service or self-hosted on one’s own infrastructure. The cloud option requires no maintenance and is well suited to those beginning their work. Self-hosting offers complete control, unlimited executions, and data residency, at the cost of administering the instance. The appropriate choice depends on scale, budget, and privacy requirements.
Conclusion
Building workflows in n8n rests on a small set of concepts: nodes, triggers, the flow of items between nodes, expressions, and deliberate error handling. A practitioner who understands these fundamentals can automate a remarkable range of tasks, and the same principles underpin even the largest production systems.