Release notes

New features and bug fixes for n8n.

You can also view the Releases in the GitHub repository.

Stable and Beta versions

n8n releases a new minor version most weeks. The stable version is for production use. beta is the most recent release. The beta version may be unstable. To report issues, use the forum.

Current stable: 2.25.6 Current beta: 2.26.2

How to update n8n

The steps to update your n8n depend on which n8n platform you use. Refer to the documentation for your n8n:

• Cloud
• Self-hosted options:
  • npm
  • Docker

Semantic versioning in n8n

n8n uses semantic versioning. All version numbers are in the format MAJOR.MINOR.PATCH. Version numbers increment as follows:

• MAJOR version when making incompatible changes which can require user action.
• MINOR version when adding functionality in a backward-compatible manner.
• PATCH version when making backward-compatible bug fixes.

Older versions

You can find the release notes for older versions of n8n: 1.x and 0.x

[email protected]

View the commits for this version.
Release date: 2026-06-10

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-09

This release contains bug fixes.

Contributors

n8n-cat-bot[bot]
sinehypernova-0718
ColinHebert
Rohit-Gahlawat
bao0541
ABDULALMAS
hammadxcm
ericyangliu
kisst
adilsitos
IchordeDionysos

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-10

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-08

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-05

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-05

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-04

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-03

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-02

This release contains bug fixes.

Contributors

n8n-cat-bot[bot]
kayjix
hammadxcm
maxabaumgarten

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-05

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-04

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-01

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-28

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-06-01

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-31

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-28

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-27

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-26

This release contains bug fixes.

Contributors

strzeluk
n8n-cat-bot[bot]
lucamattiazzi
aikido-autofix[bot]
sinehypernova-0718
thisisvaishnav

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-27

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-25

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-22

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-21

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-19

This release contains bug fixes and features.

Connect to MCP servers with less setup

Connect your agent to select MCP servers without setting up an MCP Client node and credential by hand. Pick a server from the nodes panel, sign in, and it's available to your agent.

Initial coverage includes some of the most used services in the official MCP registry, including Apify, Linear, monday.com, Notion, and PostHog. We'll expand the list to cover more services soon.

If you need to connect to an MCP server that isn't in the list, you can still use the MCP Client node with manual configuration.

Contributors

kimsehwan96
sinehypernova-0718
manuelgruber
muzahmood
mvanhorn
ABDULALMAS
ChrisJr404
aikido-autofix[bot]
KhadyotTakale
rajats-dev
TheMazeIsAmazing
onyxraven
fendy3002

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-27

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-21

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-21

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-20

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-15

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-14

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-13

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-12

This release contains bug fixes.

Contributors

etairl
devareddy05
aikido-autofix[bot]
sudarshan12s

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-18

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-15

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-15

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-14

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-08

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-07

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-07

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-07

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-06

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-05

This release contains bug fixes and features.

Microsoft Agent 365 Trigger node

The Microsoft Agent 365 Trigger node lets you build n8n agents that show up as members of your team inside Microsoft 365 apps. Once deployed, your agent gets its own identity in your Microsoft tenant, with an email address you can @mention in Teams, send email to, or grant permissions to a SharePoint site, just like a teammate.

A Microsoft Agent 365 Trigger node with a chat model, memory, and tools across Zendesk, Salesforce, PagerDuty, Datadog, and a sub-workflow.

How it works

You build the agent in n8n using the Microsoft Agent 365 Trigger node:

• Add a system prompt and give the agent access to tools, MCP servers, and your existing workflows using sub-workflows as tools.
• Set up the agent on the Microsoft side (see the Microsoft Agent 365 documentation for the configuration steps). This gives the agent an Entra ID identity with an email address that you can @mention, email, or grant SharePoint permissions to.
• Microsoft handles identity, lifecycle, security, and compliance for the agent on their side (via Entra ID, Purview, and Defender). n8n handles workflow-level governance like RBAC, credential management, and execution logs.

Things to keep in mind

• If you already use n8n with Microsoft services through individual nodes (Outlook, Teams, SharePoint, and so on), those workflows continue to work as before. Agent 365 is a new path for teams that want their agents to show up inside Microsoft apps and interact like a member of the team.
• The node requires a Microsoft 365 tenant.

For the full launch story, see the n8n blog post.

Insights data duration

Self-hosted instances can now retain insights data for up to 365 days by default, with a configurable maximum of 730 days. Retention is controlled by the new N8N_INSIGHTS_MAX_AGE_DAYS environment variable and is no longer tied to license logic. See the insights docs.

Contributors

jjnyn
haimingZZ
majiayu000
moseoh
Omc12
Gulianrdgd
jeanibarz
uppinote20

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-07

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-06

This release contains bug fixes.

[email protected]

View the commits for this version.
Release date: 2026-05-06

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-01

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-30

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-29

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-28

This release contains bug fixes and features.

IdP role mapping inside n8n (Enterprise)

Instance admins can now define group-to-role mappings inside n8n instead of encoding n8n-specific role logic in the IdP. With JIT provisioning enabled, admins write expressions against SAML attributes or OIDC claims to assign instance and project roles automatically at login. The IdP only needs to send standard group membership data: n8n handles the mapping, and role assignments are re-evaluated on every login, so access stays in sync without IdP changes.

Open Settings → SSO, pick Instance roles via SSO or Instance and project roles via SSO under User role provisioning, switch the mapping card from "Map rules on your IdP" to "Map rules inside n8n", and add expressions using the $claims object to match users for each role. Expression-based matching handles non-standard group structures that plain string matching can't reach.

Availability. Enterprise and Business.

Instance bootstrapping (Enterprise)

n8n can now be fully configured at startup through environment variables. Owner accounts, SSO (OIDC and SAML), security policies, and log streaming destinations are all applied on first boot, with no manual UI interaction required. Fields managed this way are locked in the UI and re-applied on every restart.

This makes deployment configuration the single source of truth, so you can stand up a fully configured instance from a single Helm chart or Docker Compose file, including SSO and security policy, before any user logs in.

Availability. Enterprise.

Contributors

abhishekDeshmukh74
jeanibarz
yetval
corazzione
kuishou68
MDub3y
aikido-autofix[bot]
Vitalini
sinehypernova-0718
nihaals
yuniq-neko
patdt
pedrodicati
GauthierPLM
Gulianrdgd

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-04

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-05-01

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-28

This release contains bug fixes and features.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-27

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-24

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-22

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-21

This release contains bug fixes.

Contributors

jcampbell
robrown-hubspot
rahulps1000

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-27

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-24

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-23

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-22

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-22

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-20

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-16

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-15

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-13

This release contains bug fixes and features.

Public API improvements

• Project scoping on workflow creation. POST /api/v1/workflows now accepts an optional projectId to place new workflows in a specific project. Omitting it preserves prior behaviour (workflow lands in the caller's personal project).
• Insights summary endpoint. GET /api/v1/insights/summary with optional startDate, endDate, and projectId query params. Returns successes, failures, runtime, and time saved. Requires an API key with the insights:read scope and is gated by the Enterprise insights license feature.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-04-15

This release contains bug fixes.

[email protected]

View the commits for this version.
Release date: 2026-04-07

This release contains bug fixes and features.

Token exchange authentication for embedded access (Enterprise)

n8n now supports OAuth 2.0 Token Exchange (RFC 8693) as a second authentication mechanism alongside API keys. Two scenarios are covered: seamless iframe embedding, where users see n8n inside another product without a separate login screen, and delegated API access, where a system acts on behalf of a user with full audit attribution.

The embedding system holds an asymmetric private key and signs short-lived JWTs with user identity claims. n8n verifies the signature using the configured public key, just-in-time provisions the user on first encounter, and issues a session cookie or scoped API token depending on the flow. Both subject and actor are preserved in the audit trail, so every action shows both who requested it and who performed it.

Availability. Enterprise. Requires an asymmetric key pair configured via N8N_TOKEN_EXCHANGE_TRUSTED_KEYS. Uses role-based scoping.

Execution data redaction (Enterprise)

Instance and project admins can now redact execution data. When enabled, sensitive data from production runs is never displayed in the UI, and isn't fetched from the database until a user with the reveal permission explicitly requests it. Manual executions can be left fully visible so developers can keep building and debugging without interruption. Every reveal is logged as an audit event.

Redaction is configured per workflow under Workflow settings, and reveal access is granted via project or instance settings to specific users only. See the execution data redaction docs.

Availability. Enterprise.

Public API improvements

• Community packages. Install, list, update, and uninstall community packages programmatically through new endpoints under /api/v1/community-packages. Each operation requires an API key with the matching communityPackage:* scope.
• Insights scope. A new insights:read API key scope, setting up the insights summary endpoint that ships in v2.17.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-30

This release contains bug fixes and features.

OpenTelemetry support for workflows

n8n now emits OpenTelemetry traces for workflow executions. Runs become traces in your existing OpenTelemetry backend, with no sidecars, custom exporters, or timing hacks. Teams already using Jaeger, Datadog, Grafana Tempo, Honeycomb, New Relic, or Splunk see n8n alongside everything else they observe.

Each execution appears as a root trace span with workflow ID, name, execution ID, status, duration, node count, and project info as span attributes. Failed runs surface error details on the span, so you can search and alert on workflow failures from the same tools that watch the rest of your stack.

Enable by pointing n8n at any OTLP-compatible collector. Minimum config is two environment variables:

N8N_OTEL_ENABLED=true
N8N_OTEL_EXPORTER_OTLP_ENDPOINT=http://your-collector:4318

Standard OTel variables (OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME) are also respected.

This is the foundational T1 feature. It was extended across later releases: node-level spans (v2.16), workflow version IDs in spans and distributed trace context propagation (v2.18 to v2.19), and AI Agent telemetry (v2.20).

Availability. Free, Pro, and Enterprise.

Contributors

manusjs

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-26

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-24

This release contains bug fixes.

Contributors

pkaya89
kesku

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-26

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-20

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-18

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-16

This release contains bug fixes and features.

Visual diff comes to version history

Open version history, click Compare changes, pick any two versions, and the canvas renders both side by side with changed nodes highlighted. A change count badge on each version helps you spot significant edits at a glance.

Visual diff is available on Cloud Pro and above.

Project-scoped external secrets: full team access (Enterprise)

What's new:

• Project admins manage their own vault connections from project settings.
• Project editors can use project-scoped secrets in credentials once the instance admin enables access.
• Custom roles now include five secrets scopes: list, read, create, update, and delete.
• Instance admins/owners no longer need to be project members for secrets to resolve.

For instance admins: go to Settings > External Secrets and enable the System Roles toggle, or use custom roles for more granular control.

For project admins: go to Project Settings > External Secrets to create and manage project-level connections. Instance-level connections shared with you appear as read-only.

Refer to External secrets for more information. Project-scoped external secrets are available on n8n Enterprise.

Folder-based filtering in the push and pull dialog (Enterprise)

The push and pull dialogs now include a Folder filter alongside Status and Owner. Selecting a folder scopes the list to workflows in that folder and its subfolders, shown as a hierarchical tree with folder-level checkboxes. Text search also matches folder names.

Folder-based filtering is available on n8n Enterprise (requires Environments configured).

Contributors

tbigby-kristin
ajuijas
ByteEVM
mjain
bram2w

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-13

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-11

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-09

This release contains bug fixes and features.

1Password is now available as an external secrets provider (Enterprise)

n8n now supports 1Password Connect Server as an external secrets provider, alongside HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and GCP Secret Manager.

Secrets are fetched at runtime and never stored in n8n: 1Password stays the single source of truth. Multi-field items are available as structured sub-paths: $secrets.<vault>.<item>.<field>.

How to connect

1. Deploy a 1Password Connect Server and create an access token scoped to the vaults n8n should read.
2. In n8n, go to Settings > External Secrets, select 1Password, and enter your Connect Server URL and token.

Requires self-hosted 1Password Connect Server with read-only access. 1Password as an external secrets provider is available on n8n Enterprise.

Contributors

github-actions[bot] amenk
bpk9

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-13

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-13

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-06

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-04

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-02

This release contains bug fixes and features.

Easier credential setup on Cloud

Setting up credentials on n8n Cloud is now much simpler. For supported services, just click the Connect button, authenticate with the service, and you're ready to go. Skip the manual setup for Slack, Firecrawl, HubSpot, GitHub, Google Calendar, PagerDuty, Apify, and more.

Setting up Slack credentials with managed OAuth.

Things to keep in mind

• If you prefer to use your own OAuth configuration, you can still switch to manual setup from the auth mode dropdown at any time.
• This feature is only available on n8n Cloud, where n8n manages the OAuth apps on your behalf.

Custom roles: Assignments tab (Enterprise)

Instance admins now have a dedicated Assignments tab on each custom role showing every user assigned to that role, which project they're in, and a direct link to manage them — no more navigating project by project.

Custom roles are available on n8n Enterprise.

Project-scoped external secrets: instance admin setup (Enterprise)

Instance admins can now create vault connections scoped to a specific project. Secrets from that connection appear only within that project's credentials, not across the instance. Instance-level connections are unaffected.

Refer to External secrets for more information. Project-scoped external secrets are available on n8n Enterprise.

Workflow execute as a separate permission scope (Enterprise)

workflow:execute is now a distinct scope in custom project roles, separate from editing and publishing. Users can be granted run access without being able to modify the workflow, which is a common compliance requirement for sensitive workflows.

This scope is available on n8n Enterprise.

Contributors

ByteEVM
onyxraven

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-06

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-03-04

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-27

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-23

This release contains bug fixes and features.

Multiple connections per external secrets provider

You can now set up more than one connection for a single external secrets provider. The updated UI makes it easier to configure and manage multiple connections under the same provider type.

Performance improvements for large workflow and credential volumes

Improved the reliability of the workflows and credentials listing pages for large-scale instances, reducing loading times by 30% to 80%.

Contributors

peteawood
horiyee

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-27

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-25

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-23

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-18

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-16

This release contains bug fixes.

Contributors

ByteEVM LudwigGerdes

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-13

This release contains a bug fix and features.

Personal space policies (Enterprise)

A new Security & policies settings section provides a central place for enforcing security requirements on your instance. In addition to the existing two-factor authentication enforcement, admins can now control what users can do in their personal spaces.

Available policies include:

• Sharing: control whether users can share workflows and credentials from their personal space.
• Workflow publishing: control whether users can publish workflows from their personal space.

This release builds on the recent updates to the permissions model, including custom project roles, to better support policy-driven governance.

Personal space policies are available on n8n Enterprise.

The new Security & policies settings section.

Custom roles: improved discoverability and permission visibility (Enterprise)

The project role selector now separates built-in system roles and custom roles into distinct sections, making it easier to find and choose the right role. Hovering over a role shows a summary of its configured permissions, with an option to view the full permission details.

System roles and custom roles are now displayed in separate sections.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-12

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-11

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-13

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-11

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-09

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-06

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-09

This release contains bug fixes and features.

Stronger external secrets validation (Enterprise)

n8n now verifies that the current user has access to the referenced vaults before allowing a credential that uses $secrets... expressions to be saved. If access is missing, the save operation fails. This prevents secret values from being exposed through guessed secret paths.

Improved API auditability (Enterprise)

API endpoints have been expanded to provide clearer visibility into project membership and credentials:

• GET /projects/{projectId}/users returns all members of a project including their assigned role.
• GET /credentials returns a paginated list of all credentials across the instance, including the project they belong to.

This makes it easier to audit who has access to which projects and credentials without manually reviewing each one in the UI.

More granular workflow permissions

Workflow publishing permissions for custom roles have been split into two separate scopes: workflow:publish and workflow:unpublish. This enables more precise access control in governance scenarios where unpublishing needs to be managed independently.

Performance and stability improvements

• Improved performance for instances with very large user counts, reducing slowdowns caused by user-related operations.
• Fixed a high-memory issue that could cause crashes during Source Control push flows in large deployments with many workflows and credentials.

Minor fixes

• Canvas: improved node repositioning on insertion to reduce overlaps and spacing issues.
• Log streaming: fixed proxy configuration handling for webhook destinations so requests work reliably when a proxy is configured.

Deprecated nodes

Motorhead node

The Motorhead memory node is now deprecated because the Motorhead project is no longer maintained. The node is hidden from the nodes panel for new selections, but existing workflows using this node will continue to work.

Contributors

AmitAnveri
derandreas-dt
ongdisheng
vCaisim

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-04

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-03

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-02

This release contains bug fixes.

Contributors

LostInBrittany
adriencohen
ibex088
rutgere-indeed

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-29

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-02-02

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-29

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-28

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-28

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-22

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-26

This release contains bug fixes.

Human-in-the-loop for AI tool calls

You can now require explicit human approval before an AI Agent executes specific tools.

Human-in-the-loop (HITL) for AI tool calls enforces review directly at the tool level. A gated tool cannot execute unless a human explicitly approves the action, giving you deterministic control over high-impact operations like deleting records, writing to production systems, or sending high-impact emails. This removes the uncertainty of prompt-based safeguards and insulates you from probabilistic agent behavior.

Because the review step is implemented using standard n8n integrations, approvals are not limited to a single user or interface. Decisions can be routed across people and systems, enforcing approval from the right person using the channels they already work in.

What you can do

• Require explicit human approval for any tool the agent can call, including the MCP Client tool or sub-workflows exposed as tools
• Apply approval selectively, so some tools execute autonomously while others require review
• Route approvals across users and channels (for example, send a Slack-initiated action for approval by another user via email)
• Add safety checks for high-impact or potentially destructive operations without complex workflow patterns or brittle prompt logic.

How to use it

Start with a workflow where an AI Agent is connected to one or more tools.

1. On the connection from the AI Agent to the tool you want to gate, click the + icon and choose Add human review step (hovering over the icon shows the tooltip).
2. The Tools panel opens with nodes you can use to handle the review step. Select the one you want to use.
3. Configure the approval step in the added node’s parameters. Depending on the integration, you can define the approver, the message they receive, the available actions (for example, approve or deny), and the associated buttons.
   

Get precise control over where human judgment is required, without limiting what your agent can do. Learn more here.

Contributors

ibex088
johnlinp
loganaden
Jameswlepage
cesars-gh
antman1p

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-20

This release contains bug fixes.

Chat node: human-in-the-loop actions

The Chat node now includes two new Actions for human-in-the-loop interactions in agentic workflows:

• Send a message: send a message to the user and continue the workflow
• Send a message and wait for response: send a message and pause execution until the user replies. Users can respond with free text in the Chat or by clicking inline approval buttons, as defined in the node’s configuration.

These Actions can be used as deterministic workflow steps or as tools for an AI Agent, enabling multi-turn human interaction within a single execution when using the Chat Trigger.

When used as an agent tool, the agent can ask for clarification before proceeding, helping it better interpret user intent and follow instructions. Agents can also send updates during long-running workflows using these Actions.

How to

1. Trigger your workflow with the Chat Trigger node. In the node parameters, add the Response Mode option and set it to Using Response Nodes.
2. Add a Chat node later in the workflow, or add it as a tool for an AI Agent. Select one of the following operations: Send a message or Send a message and wait for response.

Keep in mind

• If you want an AI Agent to choose between sending a message or waiting for input, add two Chat tool nodes, one for each action.
• For AI Agents triggered by the Chat Trigger node, adding Send a message and wait for response is recommended so the agent can request clarification when needed.

Learn more in the Chat node documentation.

Contributors

AbdulTawabJuly
ByteEVM
sudarshan12s
KaanAydinli

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-15

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-16

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-16

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-14

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-13

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-09

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-12

This release contains bug fixes.

TLS support for Syslog log streaming

The Syslog log streaming destination now supports TLS over TCP for encrypted connections. This enables secure log streaming to enterprise SIEM and observability platforms that require encrypted transport. With this release, log streaming is now compatible with a broader range of enterprise SIEM platforms.

Update credentials via API

n8n's public API now supports updating existing credentials by ID via a new PATCH /credentials/:id endpoint. Previously, credentials could only be created through the API so any changes required deleting and recreating the credential.

When updating, you can either replace all credential data at once (useful for bulk updates) or set isPartialData: true to merge changes with existing data. Ideal for automated secret rotation or fixing individual values without losing your configuration.

Contributors

JonLaliberte
davidpanic
TomTom101
garritfra
maximepvrt

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-13

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-13

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-07

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-08

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-06

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-05

This release contains bug fixes.

Contributors

Shashwat-06
ByteEVM
mithredate
belyas
saurabhssonkar

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2026-01-05

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-30

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-30

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-23

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.

Release date: 2025-12-22

This release contains bug fixes.

More granular workflow permissions within Custom Project Roles (Enterprise)

Custom Project Roles allow you to define fine-grained permissions at the project level. With this release, workflow permissions have been further refined by separating workflow editing from workflow publishing.

This change makes it easier to align access controls with internal processes where building workflows and publishing them are handled by different users or teams.

Custom Project Roles

Log streaming: More audit events for improved observability

Log streaming now includes additional audit events to improve visibility into operational and security-relevant changes.

This update adds events for manual workflow cancellations and workflow activation/deactivation (publish/unpublish), variable lifecycle events (create/update/delete), and user management actions (including enabling/disabling 2FA).

Workflow settings updates are also logged with the specific parameters that changed (for example, selecting a new error workflow), instead of a generic “updated” event.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-22

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-17

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-17

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-16

This release contains bug fixes and features.

Time Saved node

Previously, teams could only track a single fixed time saved value for each workflow regardless of which path an execution takes. The new Time Saved node enables more precise time savings calculations where different execution paths will save different amounts of time.

With this release you can now:

• Choose fixed value or dynamic time tracking: Use fixed time saved for simple workflows, or use one or many time saved nodes to calculate savings dynamically based on the actual execution path taken
• Configure per-item calculations: When using the Time Saved node, choose whether to calculate time saved once for all items or multiply by the number of items processed

The new Time Saved node provides increased accuracy for complex workflows where different execution paths save different amounts of time.

n8n automatically totals the time from all Time Saved nodes executed during each workflow run and reports it within the insights dashboard.

Contributors

Akcthecoder200
rishiraj-58
rlafferty

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-12

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-10

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-05

Major Version Change

n8n 2.0.0 is a hardening release, not a feature release. It strengthens n8n's position as an enterprise-grade platform with secure-by-default execution, removal of legacy options that caused edge-case bugs, and better performance under load. The goal is a more predictable foundation you can rely on for mission-critical workflows.

This release is currently in beta. There's no urgency to upgrade immediately — take time to review the breaking changes and assess your workflows using the migration tool before upgrading.

For the full story behind 2.0, read our announcement blog post.

Breaking changes

Version 2.0 includes breaking changes across security defaults, data handling, and configuration. Key changes include:

• Task runners enabled by default (Code node executions now run in isolated environments)
• Environment variable access blocked from Code nodes by default
• ExecuteCommand and LocalFileTrigger nodes disabled by default
• In-memory binary data mode removed

Review the complete list and migration guidance in the v2.0 breaking changes docs.

Before you upgrade

Use the Migration Report tool to identify workflow-level and instance-level issues that need attention before upgrading.

See the v2.0 migration tool docs for details.

Product updates

Publish / Save workflow paradigm

n8n 2.0 introduces a safer approach to updating live workflows. The Save button now preserves your edits without changing production. A new Publish button lets you explicitly push changes live when ready. See Publish workflows for details.

Canvas and navigation improvements

Subtle refinements to the workflow editor canvas and reorganized sidebar navigation.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-05

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-04

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-04

This release contains a bug fix.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-04

This release contains bug fixes.

For full release details, refer to Releases on GitHub.

[email protected]

View the commits for this version.
Release date: 2025-12-02

This release contains bug fixes.

Contributors

farzad528

For full release details, refer to Releases on GitHub.

Older versions

You can find the release notes for older versions of n8n: 1.x and 0.x

Chat with the docs

This page was Helpful Not helpful

Thanks for your feedback!

Submit