Nodes

Nodes are the building blocks of every n8n workflow. Each node performs a single, well-defined operation -- receiving data, processing it, and passing results to the next node in the chain. n8n ships with over 400 integrations as pre-built nodes.

Node Types

Trigger Nodes

Trigger nodes start a workflow. Every active workflow must have at least one trigger node. They listen for an event and produce the initial data that flows downstream.

Examples: Webhook, Schedule Trigger, Gmail Trigger, Kafka Trigger.

Action Nodes

Action nodes perform operations against external services or on the data itself. They receive items from upstream nodes, execute their configured operation, and output the result.

Examples: Google Sheets (append row), Slack (send message), HTTP Request, Postgres (execute query).

Core / Helper Nodes

Core nodes handle logic, flow control, and data manipulation within a workflow. They do not connect to external services.

Node	Purpose
IF	Branch based on a condition
Switch	Branch into multiple paths based on value matching
Merge	Combine data from two or more branches
Set	Create or overwrite fields on items
Code	Run custom JavaScript or Python
Split In Batches	Process items in configurable batch sizes
No Operation	Pass data through unchanged (useful for organization)

Adding Nodes

1. Click the + button on the canvas or on an existing node's output connector.
2. Search by name or browse by category in the node panel.
3. Select the node to add it to the canvas.

Configuring Nodes

Each node has a parameter panel on the right side of the editor. Common configuration includes:

• Credential -- select or create the authentication credential the node should use.
• Resource / Operation -- choose what the node acts on (e.g., "Message > Send" in Slack).
• Parameters -- operation-specific fields. Most fields accept static values or expressions.

Tip

Pin sample data on a node's output to speed up downstream development without re-executing upstream nodes every time.

Chaining Nodes

Drag from one node's output handle to another node's input handle to create a connection. Data flows left to right through these connections as an array of JSON items. A node can have multiple output connections (branching) and multiple input connections (merging).

Warning

If a node has no input connection and is not a trigger node, it will never execute during a workflow run.

Related tips: Workflow Architecture, Code Node Mastery

See Also

• Connections & Data Flow
• Triggers
• Expressions & Variables
• Code Node Mastery