Upgrade check n8n

Upgrade report

The node versions used by Simone Corso, tested against n8n 3.0.1.

real services started for this test, page 4.

Redis, SSH server, Web server, Supabase

Before you upgrade

1 node version not in the target. Workflows that use it will not run after the upgrade.
88 operations without a test. Availability in the target was still checked for every node version.
21 tests passed on n8n 3.0.1 against real services.

Instance: Simone Corso
Upgrade: 2.43.0–2.43.8 → 3.0.1
Current release read from the database migrations
Execution mode: Regular
Input: Node inventory from your instance
Date: October 28, 2026

All tests passed

2.43.0–2.43.8 → 3.0.1

87In use

39Behind

1Not in target

Every test passed, but 1 node version you use is not available in n8n 3.0.1.

Summary

Results at a glance

87Node versions in use

47At default

39Behind default

1Not in target

29/117Operations tested

21/21Tests passed

Availability in n8n 3.0.1

47 At default39 Behind1 Not in target

Test result per operation in use

29 Pass88 Not covered

Steps behind the target's default version

0 is the default version. Older versions keep running after the upgrade.

Most used node types

No action needed Needs attention

Summary

What needs attention

Node type	Version	Operation	Availability	Test
@n8n/n8n-nodes-langchain.toolSerpApi	1		not in target	not covered

How to read this

Behind is not a problem in itself. Older node versions keep running after an upgrade; the count is how many versions the target ships between yours and its default.
Not in target means workflows that use that node version will not load or run after the upgrade. Deprecated means the target refuses to import workflows that contain the node; replace it before upgrading.
Not covered means no test exercises that exact version yet. It is neither a pass nor a fail.

Real services n8n

Tested against real services

Real services started for this test

The nodes you use that talk to databases, message queues, mail and file servers ran against the real software, started next to n8n 3.0.1 for this test. Not mocks, not simulations.

4 of 4 services passed every test. Each service was created for this run and deleted at the end, with throwaway data and credentials.

Redispass

redis:8-alpine

memoryRedisChat 1.6, redis 1, vectorStoreRedis 1.3

SSH serverpass

linuxserver/openssh-server:10.3_p1-r1-ls239

ssh 1

Web serverpass

nginx:1.27-alpine

extractFromFile 1.1, httpRequest 4.5, rssFeedRead 1.2

Supabasepass

nginx:1.27-alpine

supabase 1, vectorStoreSupabase 1.3

What you use n8n

What you use

63 node types, 87 node versions and 117 operations, in 664 nodes. The full list, one row per node type, version and operation, is in report.csv.

Nodes per category

Needs attentionPartly testedNot coveredEvery test passed

Node types, most used first, with the versions in use

@n8n/n8n-nodes-langchain.toolSerpApi1v 1

if47v 2 · 2.2 · 2.3

set37v 3.3 · 3.4 · 3.5

merge15v 3.1 · 3.2

supabase14v 1

@n8n/n8n-nodes-langchain.chainLlm13v 1.5 · 1.9

rssFeedRead7v 1.1 · 1.2

@n8n/n8n-nodes-langchain.vectorStoreSupabase4v 1.3

filter3v 2 · 2.3

telegram44v 1.2

dataTable42v 1.1

slack23v 2.2 · 2.3 · 2.4 · 2.7

stickyNote23v 1

whatsApp16v 1.1

googleSheets15v 4 · 4.7

scheduleTrigger15v 1.2 · 1.3 · 1.4

respondToWebhook14v 1 · 1.1 · 1.5

webhook13v 1.1 · 2 · 2.1

executeWorkflowTrigger12v 1.1 · 1.2

limit12v 1

manualTrigger11v 1

@n8n/n8n-nodes-langchain.lmChatOpenRouter9v 1

gmail9v 2.1 · 2.2

@n8n/n8n-nodes-langchain.toolWorkflow8v 2.2

@n8n/n8n-nodes-langchain.lmChatMistralCloud5v 1

@n8n/n8n-nodes-langchain.lmChatGoogleGemini4v 1.1

@n8n/n8n-nodes-langchain.outputParserStructured4v 1.3

airtable4v 2.2

executeWorkflow4v 1.3

convertToFile3v 1.1

discord3v 2

errorTrigger3v 1

html3v 1.2

splitOut3v 1

summarize3v 1.1

@n8n/n8n-nodes-langchain.anthropic2v 1

aggregate2v 1

readWriteFile2v 1.1

@n8n/n8n-nodes-langchain.memoryBufferWindow1v 1.3

dateTime1v 2

formTrigger1v 2.2

gmailTrigger1v 1.3

googleCalendarTool1v 1.3

googleDrive1v 3

What you use n8n

What you use, continued

hackerNews1v 1

httpRequestTool1v 4.5

n8nTrainingCustomerDatastore1v 1

notion1v 2.2

whatsAppTrigger1v 1

xml1v 1

code94v 2

httpRequest54v 4 · 4.2 · 4.4

switch9v 3.2 · 3.4

wait8v 1 · 1.1

ssh7v 1

@n8n/n8n-nodes-langchain.agent6v 3.1

@n8n/n8n-nodes-langchain.lmChatOpenAi5v 1.3

@n8n/n8n-nodes-langchain.embeddingsOpenAi4v 1.2

redis4v 1

@n8n/n8n-nodes-langchain.documentDefaultDataLoader3v 1.1

splitInBatches3v 3

sort2v 1

noOp1v 1

Needs attentionPartly testedNot coveredEvery test passed

How the test was made n8n

What we did

From your instance

inventory.csvRead-only query

Node type	Version	Nodes
code	2	90
if	2.3	38
telegram	1.2	34
httpRequest	4.4	31
set	3.4	29

and 112 more

In an isolated test environment

Started for this run

n8n 3.0.1Task runnerRedisSSH serverWeb serverSupabaseModel stand-in

21 test workflows executed

Step 01 · Your instance

An inventory, nothing else

One read-only query on the n8n database listed each node type and version in use, with counts. Your workflows, credentials and execution data stayed in your environment.

Step 02 · Test environment

The target release, isolated

A fresh n8n 3.0.1 started with its task runner, with Redis, SSH server, Web server, Supabase. Only the test workflows that exercise your node versions ran, and the environment was deleted afterwards.

Step 03 · This report

A result per node version

Each node version you use is marked pass, fail or not covered, with whether n8n 3.0.1 still ships it and how far it is from the default version.

What changes n8n

What changes for you

n8n publishes the changes that can require action when you upgrade. These are the ones between 2.43.0–2.43.8 and 3.0.1. Only the changes that name a node you use are listed.

Release	Change and nodes	What to do
3.0.0	Removed nodes Read/Write Files from Disk Supabase Vector Store Default Data Loader OpenAI Chat Model HTTP Request Tool Schedule Trigger Convert to File HTTP Request Summarize Split Out Aggregate Supabase AI Agent Limit Sort Code HTML	Workflows that use a removed node fail. Before you upgrade, Settings > Migration Report lists the affected workflows on your instance, and the Deprecated and versioned nodes page tracks the final version of every node listed here. -… Source
3.0.0	Execute Sub-workflow node: Local File and URL sources removed Execute Sub-workflow	n8n 3.0 removes the Local File and URL options from the Source parameter of the Execute Sub-workflow node. Only node versions 1.1 and older offered them. Nodes that still use one of these sources fail with an error. What to do: Import the… Source
3.0.0	$evaluateExpression() removed from the Code node Code	n8n 3.0 removes the $evaluateExpression() convenience method from the Code node (JavaScript). Only task runners in insecure mode (N8N_RUNNERS_INSECURE_MODE=true) are affected. Secure-mode runners, the default since n8n 2.0, already fail on… Source
3.0.0	AI Agent node: Older agent modes removed AI Agent	Version 1 of the AI Agent node supported several agent type modes, including SQL Agent, Conversational Agent, OpenAI Functions Agent, Plan and Execute Agent, and ReAct Agent. n8n 3.0 removes version 1 of the node, along with these modes.… Source
3.0.0	Gmail Trigger node: Older versions run as version 1.4 Schedule Trigger Gmail Trigger Gmail	n8n 3.0 removes the separate behavior of Gmail Trigger node versions 1 to 1.3. Workflows that use these versions keep loading, but the node runs with the version 1.4 behavior: * Max Emails per Poll applies to every poll. The default is 10… Source
3.0.0	Slack API credential requires the signing secret Slack	n8n 3.0 requires a signing secret on the Slack API credential. The Slack Trigger node verifies incoming requests against it, and version 2 of the node makes the field required. When you need to act depends on how you use the credential: -… Source
3.0.0	Changed defaults and removed variables Code	- Unverified community packages off by default. The default for N8N_UNVERIFIED_PACKAGES_ENABLED changes from true to false. After the upgrade, you can't install unverified community nodes from npm, and installed ones stop loading. - What… Source

Scope

What this test covers, and what it does not

Covered

Availability of every node version in use, read from the node catalog of n8n 3.0.1 itself.
Behavior of 29 of the 117 operations in use, at the exact node version, against real Redis, SSH server, Web server, Supabase instances.
AI nodes are tested against a deterministic stand-in for the model provider: n8n's requests, response handling, tools, memory and vector stores are checked; the model's answers are not.

Not covered

Nodes for cloud services with a fixed endpoint, such as Slack, HubSpot, Google and Salesforce. They are listed with their availability and marked not covered.
Trigger nodes such as Webhook and Schedule: the test environment starts workflows manually.
Queue mode, multi-instance deployments, and the business logic of your own workflows.

Your data

The only input is the inventory: node type, version and counts.
No workflow, credential or execution data was requested or used.
The test environment was created for this run and deleted at the end.

Recommended next steps

Start with what needs attention on page 3. Node versions without a test can be added to the suite on request, and the inventory shows which ones matter most to you. Back up the database before you upgrade, and try critical workflows on a staging instance first.