n8n 2.46: what's new and should you upgrade

n8n 2.46.0 was released on October 27, 2026 on the beta track, followed by 2.46.1 on October 28. The change you'll notice first: you can now use your personal credentials in team projects without sharing them, and every workflow run acts as a specific person, which can disable Execute and Publish for teammates. For production, the current stable release is 2.45.5.

2.46 shipped on the same day as the n8n 3.0 beta, and it's the 2.x side of the same code: every entry in the 2.46.0 changelog also appears in 3.0.0's. What 2.46 leaves out are 3.0's breaking changes, so this is the version to use to get your instance ready for 3.0.

The short version

• Which version to run: on October 29, 2026, npm's stable and latest tags point to 2.45.5, and beta and next to 2.46.1. Docker Hub's tags match.
• Personal credentials in team projects: you can pick your own credentials in any team project you're a member of. Teammates who can't use them see the workflow but can't run or publish it, and n8n hides the execution data from them.
• Migration Report for 3.0: export to CSV, a new "Executions might fail" impact, filtering by project, and workflow editors can triage findings for their own workflows. 2.46.1 improves the entries for removed nodes and the Edit Image node.
• Also new: an Edit Image node v2, signature verification for the Workable Trigger node, dependency endpoints in the public API, Microsoft Foundry models in Agents, and an n8n node action to add a user to a project.
• Our upgrade test: a 2.45.5 instance upgraded to 2.46.1 without issues, and JavaScript and Python Code nodes kept working.

Should you upgrade?

• Production instances: stay on 2.45.5, the stable release. Our n8n 2.45 roundup covers what changed from 2.44, including the durable scheduler.
• Test or staging instances: try 2.46.1, especially if you use team projects with shared credentials, or if you're preparing for 3.0. n8n's 3.0 announcement recommends updating to the latest 2.x first, because it has "the newest version of the report."

Pin the exact version in Docker Compose, and give the task runner the same tag:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n:2.46.1
  task-runners:
    image: n8nio/runners:2.46.1

Take a backup before you upgrade. Our guide on how to update self-hosted n8n safely has the steps.

Personal credentials in team projects

This is the one entry n8n's curated changelog highlights for 2.46.0. In the GitHub changelog it appears as "Make granular credential sharing always on."

What changes, per n8n's docs page on using personal credentials in projects:

• You can use your own credentials in team projects without sharing them with the project first. The credential selector groups them under Available to you and Available in project name.
• Every run acts as a person. A manual run acts as whoever selected Execute. A triggered run (schedule, webhook, app event) acts as whoever last published the workflow.
• Teammates who can't use your credential see its name and owner on the node, but n8n disables Execute and Publish for them. They can switch the node to their own credential, or ask you to share yours.
• Publishing is checked. You can't publish a workflow with a credential you can't use, and the check names the credential that blocks it.
• Execution data is hidden from people who can't use a credential the execution used, including data that came back from a sub-workflow. The same applies to the public API and the n8n MCP server.
• Two access levels in the credential's Sharing tab: Can view (see that it exists and where it's used) and Can use (run and publish with it, without seeing its details).

Existing published workflows keep running, according to the changelog. Two details to know before you upgrade a shared instance:

• Owners and Admins can't use a member's personal credential in a team project unless it's shared with the project. They can see it on the node but can't run with it.
• Agents use project credentials only. AI agents and the Slack and Microsoft Teams integrations don't offer personal credentials yet.

If a workflow lost its publisher, for example because that account was deleted, the docs say to republish it so it runs as you.

Getting ready for n8n 3.0: the Migration Report

The migration report at Settings > Migration Report lists the workflows and instance settings that n8n 3.0 changes. 2.46 adds, per the changelog:

• Export as CSV.
• An "Executions might fail" impact level.
• Filtering workflows by project.
• Workflow editors can triage the findings for their own workflows.
• New migrations: automatic migration for the Edit Image node, rules for the Slack signature secret, and detection of the removed LangChain Code node.
• 2.46.1: improved entries for removed nodes and the Edit Image node.

The editor also gains "Prevent usage of deprecated nodes," which the changelog lists without more detail. We didn't test it in the editor. Through n8n's internal REST API, 2.46.1 still saved a new workflow with a Cron node, and an existing published Cron workflow stayed active after the upgrade. Cron is only removed in 3.0, where that workflow stops running.

Nodes, AI and API

New in 2.46.0, from the changelog:

• Edit Image node v2, built on napi-rs/canvas. 3.0 removes Edit Image versions 1 and 1.1, and the Migration Report can now move them over.
• Workable Trigger node: webhook signature verification.
• Webhook and MCP Trigger nodes: can authenticate requests through trusted sources.
• Chat node: Respond to Chat now works in embedded chat mode.
• n8n node: a new action to add a user to a project.
• Databricks node: the Lakebase resource and a Lakebase Chat Memory sub-node.
• Public API: dependency endpoints for workflows, credentials and data tables.
• Agents: Microsoft Foundry models (including Claude deployments on Foundry), mention-only Slack replies, a Microsoft Teams agent channel, and budget guardrail stops in the session timeline. For how these differ from the AI Agent node, see our Agents explainer.
• Observability: OpenTelemetry GenAI attributes on AI Agent and chat model spans, and configurable prefixes for custom OTel attribute keys.
• Multi-main: version mismatch warnings now show on all mains.

Fixes worth knowing about

The 2.46.0 changelog lists over 150 bug fixes. A few that change behavior you might rely on:

• Exported workflow JSON no longer includes credential names.
• Static data written by a webhook trigger is now saved.
• A workflow's own Error Trigger runs when no error workflow is selected.
• Node ID columns are widened to 64 characters, and publishing fails for stored versions with trigger node IDs over 64 characters.
• The Summarize node returns null instead of NaN for an average with no numeric values.
• HTTP Request node stops batching when the execution is cancelled, and retries stop after an execution is cancelled.
• Email Trigger (IMAP) node backs off reconnects when the server drops each new connection.
• Microsoft Teams Trigger node renews its Graph subscription through lifecycle notifications.
• JavaScript task runners have Node.js Web Storage disabled. On 2.45.5, our runner container logged a localStorage is not available warning; on 2.46.1 it didn't.

2.46.1 adds two expression fixes: the ExpressionError name is kept in minified builds, and undefined values are kept in QuickJS expression results.

What we saw when we upgraded

On October 29 we ran n8n 2.45.5 in Docker with the default SQLite database and an external task runner, published a JavaScript Code node workflow, a Python Code node workflow and a Cron workflow, and then switched both images to 2.46.1:

• Migrations ran on startup and the log recorded Recorded version change: 2.45.5 -> 2.46.1.
• JavaScript and Python Code nodes returned the same results through their webhooks as on 2.45.5.
• The published Cron workflow stayed active.
• The startup log lists deprecations that 3.0 will act on, such as the N8N_RUNNERS_TASK_TIMEOUT default dropping from 300 to 60 seconds. 2.45.5 prints the same list.

This was a small test instance, so it says nothing about migration time on a large Postgres database.

n8n 3.0 beta

n8n published 3.0.0 on October 27 and 3.0.1 on October 28 as Docker images only. Our 3.0 beta test covers what broke when we upgraded, and the 3.0 guide lists every breaking change. For all release coverage, see the releases tag.