Source: github.com/n8n-io/n8n/releases/tag/n8n%403.0.0
The 3.0.0 release, dated 27 October 2026, is marked as a pre-release on GitHub. The changelog adds a migration report that can be exported as CSV, along with v3 migration rules for the Slack signature secret. The migration also detects the removed LangChain Code node.
On the agent side, the release lets the Agent Builder set up Microsoft Foundry models and lists Foundry deployments in the Agents model selector. It also adds Claude deployments on Microsoft Foundry, a Microsoft Teams agent channel, and mention-only Slack replies for agents. n8n Connect servers can now be added to MCP registry servers.
Several defaults and removals change existing behavior. The chat hub module is now off by default, the Edit Image v1-1.1 version and some dead nodes have been removed, and N8N_NODES_API_VERSION is set to 3. Many other fixes cover agent credential checks, execution redaction and binary stream handling.
Why it matters if you build agents
Developers upgrading should run the migration report first, since workflows that use the removed LangChain Code node and the Slack signature secret may need changes. Agents that rely on the chat hub module will need to turn it back on. Builders who want Slack, Teams or Foundry-hosted models in their agents now have built-in options.
Get stories like this every weekday
One short email with the day's agent tooling news.