n8n

n8n

A fair-code, node-based workflow automation tool that allows you to connect different apps and services to automate tasks.

Node

The fundamental building block of an n8n workflow, representing a single step that performs a specific action, fetches data, or triggers a process.

Workflow

A sequence of connected nodes that automate a specific task or business process from start to finish.

Trigger Node

A special type of node that starts a workflow based on an event, such as a schedule, a webhook, or an app-specific update.

Webhook Node

A trigger node that exposes a unique URL, allowing external applications to send real-time data to kick off an n8n workflow.

Schedule Node

A trigger node used to run a workflow automatically at specific times or intervals (e.g., every hour, daily at 9 AM).

Action Node

A node that performs a specific task, such as creating a row in Google Sheets, sending a Slack message, or fetching data from an API.

Data Item

The individual units of data (JSON objects) that pass through nodes in n8n.

Input Data

The data that enters a node from the previous connected node(s) in the workflow.

Output Data

The data generated or modified by a node, which is then passed on to the next connected node(s).

JSON

JavaScript Object Notation; the data format n8n uses to structure and pass data between nodes.

Binary Data

Non-text data handles by n8n, such as images, PDFs, audio files, or spreadsheets.

Expression

A piece of code (often using JavaScript) used in n8n to dynamically fetch, manipulate, or calculate values from previous nodes.

$json

The n8n variable used in expressions to reference the JSON data of the current item.

$item(index)

An expression syntax used to reference a specific item from a previous node by its index number.

$prevNode

An n8n expression variable used to explicitly reference data from the node immediately preceding the current one.

IF Node

A conditional node that splits the workflow path into "True" or "False" branches based on specified criteria.

Switch Node

A routing node that allows a workflow to branch into multiple paths (up to 4 or more) based on matching values.

Merge Node

A node used to combine data streams from multiple branches back into a single workflow path using various connection rules.

Looping

The process of repeating a sequence of nodes for multiple items, often achieved using the Loop Over Items node or code.

Loop Over Items Node

A built-in node that simplifies processing a collection of items one by one in a loop until all items are handled.

Code Node

A powerful node that allows you to write custom JavaScript or TypeScript to transform data or execute complex logic.

HTTP Request Node

A versatile action node used to interact with external APIs by sending GET, POST, PUT, or DELETE requests.

Set Node

A node used to add, remove, or modify specific fields (variables) within the current workflow data stream.

Edit Image Node

An n8n node specifically designed to manipulate binary image data, such as resizing, cropping, or rotating.

Read/Write Files from Disk Node

Nodes used in self-hosted n8n instances to read files from or save files directly to the local file system.

Execute Command Node

A node that allows n8n to run shell commands on the host machine where n8n is running.

Credentials

Securely stored authentication data (like API keys, OAuth tokens, or passwords) used by nodes to access external services.

OAuth2

A secure authentication protocol used by n8n to connect to third-party services (like Google or GitHub) without storing raw passwords.

Community Nodes

Custom nodes built by the n8n community that can be installed to extend n8n's capabilities beyond built-in nodes.

Self-Hosting

Running n8n on your own infrastructure (like Docker, AWS, or a local machine) instead of using n8n's cloud service.

n8n Cloud

The official managed hosting service provided by n8n, removing the need to manage servers or infrastructure.

Execution History

A log within n8n that shows past runs of a workflow, including data inputs, outputs, and success/failure statuses.

Active Workflow

A workflow that is turned "On" and actively listening for triggers (like webhooks or schedules) in the background.

Inactive Workflow

A workflow that is turned "Off" and will only run when manually triggered inside the editor UI.

Error Trigger Node

A specialized trigger node that automatically kicks off a separate workflow or path when another workflow fails.

On Error Option

A node setting that defines what happens if that specific node fails (e.g., Stop Workflow, Continue Anyway).

Wait Node

A node that pauses the workflow execution for a specified amount of time (seconds, minutes, hours) or until a specific date.

Crypto Node

A utility node used to encrypt, decrypt, hash, or sign data for security purposes.

Date & Time Node

A node used to format, parse, or perform calculations (like adding days) on date and time strings.

GraphQL Node

A specialized node designed to make queries and mutations specifically to GraphQL APIs.

Pinned Data

A testing feature in n8n that locks specific test data into a node, preventing you from needing to re-run previous nodes during design.

Sub-Workflow

A separate n8n workflow that is called and executed by a parent workflow using the Execute Workflow node.

Execute Workflow Node

A node used to trigger and run another n8n workflow as a sub-task, passing data to it and receiving data back.

Environment Variables

Configuration settings applied to the n8n server host to control global behaviors like encryption keys or execution limits.

Concurrency Limit

An n8n configuration setting that controls how many workflows can run simultaneously to prevent server overloading.

Sticky Notes

Visual annotations you can add to the n8n canvas to document and explain how a workflow works to other users.

Variables (n8n Global)

Configuration variables defined at the workflow or instance level that can be reused across multiple nodes via expressions.

Data Transformation

The process of changing the structure, format, or values of data as it moves from one node to another.

Fair-Code

The licensing model n8n uses, meaning the code is visible and free for self-hosting for internal use, but restricts commercial hosting.