For the complete documentation index, see llms.txt. This page is also available as Markdown.

v3.0 Breaking changes

This document highlights breaking changes and actions to prepare for the upcoming transition to n8n 3.0, scheduled for October 2026. These updates improve security, simplify configuration, and remove legacy features.

The release of n8n 3.0 continues n8n's commitment to providing a secure, reliable, and production-ready automation platform. This major version includes important security enhancements and cleanup of deprecated features.

Deployment

Docker-based deployment required for self-hosted n8n

  • Self-hosted n8n will require a Docker-based deployment. Installations run via npm / npx n8n will no longer be supported.

  • What to do: If you currently run n8n with npm or npx n8n, plan a move to a Docker-based deployment before upgrading to n8n 3.0. For local installations, Docker Compose is expected to be the easiest path.

  • Step-by-step migration guidance will be coming soon

Removed nodes and helpers

Older nodes, modes, and helpers that have been replaced by newer patterns are being removed in n8n 3.0.

Removed nodes

  • Function node (legacy)

  • Function Item node (legacy)

  • Item Lists node (legacy)

  • What to do: Migrate affected workflows to the current recommended alternatives before upgrading:

    • Replace Function and Function Item nodes with the Code node. Use Run Once for All Items mode in place of Function, and Run Once for Each Item mode in place of Function Item.

    • Replace the Item Lists node with the node matching the operation you use: Split Out, Aggregate, Sort, Limit, Remove Duplicates, or Summarize.

Changed node behavior

  • Execute Workflow node: older behavior is being removed.

Removed expression helpers

  • The deprecated $getPairedItem expression helper is being removed.

  • What to do: Use n8n's standard item linking instead, for example the pairedItem property or $("<node-name>").item.

Security

Security defaults are getting stronger to make n8n safer by default. These changes may affect existing workflows or credentials.

  • Tighter handling of risky resource names.

  • More secure credential behavior.

  • Key rotation enabled by default.

Retired capabilities

Some legacy or lower-usage product capabilities are being retired in n8n 3.0. Guidance will be provided where a migration path or alternative exists.

  • Chat hub — being retired.

  • Workflow import from URL in the editor — being removed. Other import methods remain supported: copy-paste, Import from File in the editor UI menu, the CLI, and the Public API.

  • Non-functional nodes — being removed.


This page will be updated with full details, migration guides, and links as n8n 3.0 approaches its release.

Last updated

Was this helpful?