n8n Node Types Explained (2026) | How to Build Workflow with Triggers, Apps, Core & Actions

Overview

In this lesson, you'll learn about the different types of nodes in n8n and how they form the foundation of any automation workflow. You’ll explore how to create workflows starting with trigger nodes, followed by app, core, and action nodes, and understand how to configure these nodes. By the end, you’ll build a simple workflow that fetches data from Google Sheets, giving you practical experience with node setup, credentials, and workflow execution.

Understanding n8n Node Types

Nodes are the building blocks of n8n workflows. Each workflow is essentially a collection of interconnected nodes that perform a series of tasks, starting with a trigger node and ending with one or more action nodes. n8n classifies nodes into four main types:

1. Trigger Nodes

Trigger nodes are like alarm clocks for your automation. They wake up the workflow and start its execution when a specific event occurs. This can be:

• A new email arriving
• A form submission
• A file upload
• A scheduled time (e.g., every day at 8 a.m.)

Trigger nodes listen for these events and tell the workflow when to run. Every production workflow must start with a trigger node.

2. App Nodes (Action Nodes)

App or action nodes interact with external applications or services. They perform operations such as:

• Adding, updating, or deleting data
• Sending data to external systems
• Triggering events in other apps

Examples include sending a Slack message, updating a Google Sheet, or sending an email. You can explore more about available integrations in the n8n integrations documentation{:target="_blank"}.

3. Core Nodes

Core nodes perform generic functions within your workflow but do not directly interact with external apps. They are used for:

• Data manipulation (e.g., filtering, setting values)
• Logic processing
• Scheduling
• Making generic API calls

Some examples are the Filter node, Set node, and Code node (where you can write JavaScript or Python code). To learn how to use the Set node effectively, check out our detailed guide on the Set Node in n8n.

4. Cluster Nodes

Cluster nodes group multiple nodes to perform complex, specific functionalities. An example is an AI agent node that integrates multiple AI-related actions. This lesson will focus on the first three types, with cluster nodes covered later in the course.

Step-by-Step: Building Your First Workflow with Nodes

Let's build a simple workflow in n8n that starts with a manual trigger and fetches data from a Google Sheet.

Step 1: Create a New Workflow

1. Open your n8n workspace (cloud or self-hosted).
2. Navigate to your project folder or workspace.
3. Click on Create New Workflow.
4. Give your workflow a meaningful name (e.g., "Fetch Google Sheet Data").

Step 2: Add a Trigger Node

1. Click Add First Step.
2. Search for and select the Manual Trigger node.
3. This node will start the workflow whenever you click Execute Workflow or Test Workflow.

Step 3: Add a Google Sheets Node

1. Click the + icon next to the Manual Trigger node to add the next step.
2. In the node search, type Google Sheets and select it.
3. Choose the operation Get Rows. This operation fetches rows of data from a specific Google Sheet.

Step 4: Connect Google Sheets to Your Google Account

1. In the Google Sheets node, click on the Credentials dropdown.
2. Select Create New.
3. Choose OAuth2 as the authentication method.
4. Sign in with your Google account and authorize n8n to access your Google Sheets.
5. Once authorized, select the newly created credential.

Step 5: Configure the Google Sheets Node

1. Under Document, select the Google Sheet file you want to fetch data from (e.g., "mock orders data").
2. Under Sheet, select the specific sheet tab (e.g., "mock order data").
3. Optionally, apply filters to limit the rows fetched (skip this for now).

Step 6: Save and Test the Workflow

1. Save the workflow.
2. Click Execute Workflow or Test.
3. The Google Sheets node will fetch data and display it in the output panel.

For more details on core nodes and their configuration options, refer to the n8n Core nodes documentation{:target="_blank"}.

Understanding the Node Configuration Interface

When you open a node, you see its configuration pane:

• Top Section: Where you select credentials and main operation parameters.
• Left Panel: Shows incoming data to the node (input).
• Right Panel: Shows the node’s output after execution.

For example, the Google Sheets node receives input from the trigger (which is empty in the case of a manual trigger) and outputs rows fetched from the sheet.

Additional Node Settings

• Always Output Data: Ensures the node outputs data even if no rows are found.
• Execute Once: Runs the node only once per workflow execution.
• Retry on Fail: Determines what happens if the node encounters an error (stop, continue, or use error output).

You can rename the node to something meaningful by hovering over the node name and clicking the pencil icon (e.g., rename to "Get Orders Data").

Working with Node Outputs

After executing the Google Sheets node, you can view the output in various formats:

• Table View: Shows data in rows and columns.
• JSON View: Shows data in JSON format.
• Schema: Displays the structure of the data with field names and data types.

You can also:

• Edit Output Data: Modify data manually in the output before passing it on, which is useful for debugging or testing.
• Pin Data: Save the output data so the node doesn’t re-execute every time you run the workflow, speeding up testing and development.

If you want to extend your workflow with HTTP requests to other services, consider learning how to use the HTTP Request Node in n8n, which is a powerful integration node for API calls.

Common Mistakes & Troubleshooting

• Trigger Node Missing: Every workflow must start with a trigger node; forgetting this will prevent the workflow from running.
• Incorrect Credentials: Ensure you select or create the correct credentials for external services like Google Sheets.
• Wrong Sheet or Document Selected: Double-check you have selected the correct Google Sheet document and sheet tab.
• Node Configuration Not Saved: Always save your workflow and node configuration before testing.
• No Data Returned: Check filters or sheet permissions if your node returns empty data.
• Pinning Data Without Updating: If you pin data and then change the source sheet, the workflow will continue using the old pinned data until you unpin and re-execute.

Useful n8n Expressions for Node Configuration

You can use expressions to dynamically configure node parameters. For example, to get the current date in a Set node:

{{ $now.toISOString() }}

Or to reference data from a previous node (e.g., from a Google Sheets node named "Get Orders Data"):

{{ $node["Get Orders Data"].json["orderID"] }}

Explore more on expressions in the n8n documentation on Expressions.

Summary: How n8n Workflows Flow

1. Trigger Node: Starts the workflow based on an event or manual execution.
2. App/Core Nodes: Process, transform, or analyze data.
3. Action Nodes: Perform final operations like updating external apps or sending notifications.

For mastering workflow logic and branching, consider our lesson on Master Conditional Logic in n8n.

Quick Reference Cheat Sheet

Next Steps

Now that you understand node types and how to build a simple workflow, the next lessons will dive deeper into processing data formats like JSON and table data, advanced node configurations, and integrating more external services.

For more detailed information, check out the official n8n docs on Creating Workflows{:target="_blank"} and the Google Sheets Node{:target="_blank"}.

By following these steps and concepts, you'll be well on your way to building powerful n8n automations tailored to your needs.