n8n Documentation

What is it?

The documentation is organised into a handful of top-level sections: Using n8n (core concepts, data structure, expressions, error handling, credentials), Integrations (a reference page per node listing every operation and field), Hosting n8n (Docker, Kubernetes, environment variables, queue mode, scaling, security), Advanced AI (LangChain-based agent, chain, memory, vector store and tool nodes), Code (JavaScript and Python in the Code node), API (the public REST API for managing workflows programmatically), and Embed / Enterprise topics. Everything is versioned, and the site search is genuinely good if you query it with the right terms.

A reading order that actually works

Most people open the docs at the node page for whatever they are building and bounce off when the data does not look how they expect. The problem is almost never the node — it is the item model underneath it. Read these five pages in order once and the rest of the documentation becomes obvious.

• Using n8n → Data → Data structure — what an 'item' is and why nodes run once per item.
• Using n8n → Data → Data mapping and Expressions — $json, $node, and the expression editor.
• Using n8n → Flow logic → Splitting, merging, looping — the four control-flow nodes.
• Using n8n → Flow logic → Error handling — error workflows, retries, continue-on-fail.
• Credentials → Credential sharing and scopes — where OAuth setups usually go wrong.

Search tactics that find the answer in seconds

The docs search rewards specific technical terms and punishes natural-language questions. Search the way the documentation is written, not the way you would ask a colleague.

• Press / anywhere to focus the search box.
• Search '<Node name> pagination' or '<Node name> operations' rather than 'how do I get all rows'.
• For self-hosting, search the environment-variable name directly, e.g. N8N_ENCRYPTION_KEY.
• If a documented option does not exist in your instance, check the version selector and the release notes.
• Falling back to Google with site:docs.n8n.io often beats the on-site search for long-tail phrases.

The hosting pages you will keep coming back to

If you self-host, four pages carry most of the operational weight. Bookmark them now rather than hunting for them during an incident.

• Configuration → Environment variables — the full list, with defaults and types.
• Scaling → Queue mode — Redis, workers, and when a single instance stops being enough.
• Securing n8n — reverse proxy, HTTPS, authentication, and locking down the webhook surface.
• Updating n8n — safe upgrade order, database migrations and rollback strategy.

Docs vs blog vs forum — which source to trust

All three are useful, but they age differently. The docs are versioned and updated with each release; blog tutorials capture a snapshot of the version they were written in; forum threads are the most practical and the least maintained.

The reliable pattern: get the concept from the docs, get a working example from the blog or a template, and get the edge-case workaround from the forum — then verify that workaround against the current docs before shipping it.

Where to look for what

How to use it — step by step

1. 1Open the docs and read Data structure once, end to end — it prevents the majority of beginner errors.
2. 2Use the site search (press /) with the exact node name plus the behaviour you need.
3. 3For an integration, go Integrations → Built-in nodes → your node, and read Operations before Fields.
4. 4Check the version selector matches your running instance whenever an option seems missing.
5. 5For self-hosting, bookmark the environment-variable reference and the scaling page.
6. 6Copy code samples straight into a Code node and adapt them rather than typing from scratch.
7. 7When the docs and a blog post disagree, follow the docs and check the release notes for the change.

Quick checklist

• Read Data structure and Expressions once
• Version selector matches your instance
• Node Operations section read before building
• Error-handling page reviewed for production flows
• Environment-variable reference bookmarked (self-hosted)
• Release notes checked after every upgrade
• Security hardening page applied before exposing webhooks
• Public API reference reviewed if you automate deployments

Pro tips

• Docs pages often link to related forum threads at the bottom — that is usually the practical example you were looking for.
• Keep the docs open in a second tab while taking the Academy courses; the courses teach concepts, the docs cover node specifics.
• The API reference doubles as documentation for what the UI does under the hood when you are debugging odd behaviour.