📖 n8n Tools

n8n Nodes Explainer

Search any n8n node or paste your workflow JSON to get instant plain-English explanations — what each node does, key parameters, real-world use cases, and common mistakes to avoid.

50+ nodes explained
Plain-English descriptions
Key parameters guide
Real use cases
Common mistakes
Paste workflow JSON

n8n Nodes Explained — Plain-English Guide for Every Node Type

n8n has over 400 node types, and understanding what each one does — especially as a beginner or when reviewing a shared community workflow — can be overwhelming. This free tool gives you instant plain-English explanations for every major n8n node: what it does, when to use it, its key configuration parameters, real-world automation use cases, and the most common mistakes people make when using it.

Paste your workflow JSON to get explanations for all nodes at once, or search any node by name to deep-dive into a specific one. Ideal for n8n beginners learning automation, developers reviewing unfamiliar community workflows, and teams documenting their automation stack.

🪝

Trigger Nodes Explained

Trigger nodes start your workflow. The most important ones:

  • Webhook Trigger — starts when an HTTP POST/GET request hits a unique URL. Used for receiving data from external services like Stripe, GitHub, Typeform.
  • Schedule Trigger — runs your workflow on a cron schedule. Used for daily reports, periodic data sync, scheduled emails.
  • Manual Trigger — starts the workflow when you click "Execute" in the editor. Best for testing and one-off runs.
  • Email Trigger (IMAP) — fires when a new email arrives in an inbox. Used for email-based automation pipelines.
🔀

Logic & Flow Nodes Explained

Logic nodes control the execution path of your workflow:

  • IF node — splits workflow into two paths: true and false, based on a condition you define.
  • Switch node — routes data to one of multiple output branches based on a value, like a switch statement.
  • Merge node — combines data from two or more branches back into a single stream.
  • SplitInBatches — processes a large array of items in smaller chunks to avoid rate limits or memory issues.
  • Wait node — pauses workflow execution for a defined time or until a webhook is received.
⚙️

Data Transformation Nodes

Data nodes reshape, filter, and transform the data flowing through your workflow:

  • Set node — the most-used node. Adds, modifies, or removes fields from your data items. Think of it as a data mapper.
  • Code node — runs custom JavaScript or Python to process data. Full access to all item fields and built-in libraries.
  • Function node — older version of Code node. Still widely used in community workflows.
  • Item Lists node — splits arrays into individual items, aggregates items into arrays, or removes duplicates.
  • JSON node — parses JSON strings into objects or stringifies objects to JSON.
🤖

AI & LLM Nodes Explained

n8n's AI nodes (introduced in 2023–2024) enable powerful LLM-powered automations:

  • OpenAI node — calls OpenAI's API for text completion, chat, image generation, embeddings, and transcription.
  • AI Agent node — creates an autonomous AI agent that can use tools, memory, and make multi-step decisions.
  • LangChain nodes — a suite of nodes for building RAG pipelines, vector store queries, and chain-of-thought reasoning.
  • Anthropic node — calls Claude models for text generation and analysis.
  • Embeddings nodes — generate vector embeddings for semantic search and RAG workflows.

Frequently Asked Questions — n8n Nodes

What is the difference between the Set node and the Code node in n8n? +
The Set node is a visual, no-code way to add, modify, or remove fields from your data items. You map input fields to output fields using a point-and-click interface — no programming required. The Code node lets you write custom JavaScript or Python to process data with full programming flexibility. Use the Set node for simple field mapping and renaming. Use the Code node when you need loops, conditionals, mathematical calculations, string manipulation, or logic that can't be expressed in the Set node's UI.
When should I use the IF node vs the Switch node in n8n? +
Use the IF node when you have a binary decision — the data either meets a condition (true output) or doesn't (false output). For example: "Is the email domain @gmail.com? Yes → path A, No → path B." Use the Switch node when you need to route data to one of multiple different paths based on a value. For example: routing based on a status field that could be "new", "pending", "approved", or "rejected" — each value goes to a different branch. The Switch node is essentially a multi-output IF node.
What does the SplitInBatches node do in n8n and when do I need it? +
The SplitInBatches node processes a large array of items in smaller chunks (batches). You need it when: (1) you're hitting API rate limits — by processing 10 items at a time with a Wait node between batches, you avoid exceeding limits; (2) you have hundreds or thousands of items to process and want to avoid memory issues; (3) you need to add delays between API calls. Without SplitInBatches, n8n processes all items simultaneously, which can overwhelm rate-limited APIs or cause memory problems with very large datasets.
How does the HTTP Request node work in n8n? +
The HTTP Request node makes HTTP calls to any REST API or web endpoint. You configure the URL, method (GET, POST, PUT, DELETE, PATCH), headers, query parameters, and request body. It supports all common authentication methods: API Key (header or query param), Bearer Token, Basic Auth, OAuth2, and Digest Auth. The response is automatically parsed — JSON responses become structured data items you can use in subsequent nodes. This is the most versatile node in n8n, as it lets you connect to virtually any API that isn't covered by a dedicated integration node.