n8n News

This feed includes only recent releases, roughly from the last 12 months, not the full historical archive. That is why a long-established product may have only a few news items.

6 news

n8n
AI Assistant on self-hosted simplified to a single command in 2.35

Earlier, running AI Assistant in a self-hosted setup required manually enabling the instance-ai module and configuring the sandbox, model, and web search through env variables. In 2.35, the module is enabled by default, setup is one command, and the model provider (Anthropic, OpenAI, OpenRouter, or any OpenAI-compatible endpoint, including a local one), sandbox, and web search (native provider support or fallback to Brave Search/self-hosted SearXNG) are configured directly in the UI.

n8n lets each instance choose its model, including a local OpenAI-compatible endpoint, without requiring the vendor's cloud; it does not provide centralized routing or quotas across multiple instances like a dedicated gateway. LLM Gateway →
n8n
n8n is discussing dropping npm installation in favor of Docker only

The team has opened for public discussion the phase-out of native npm installation for the self-hosted instance. Docker will become the only officially supported deployment method. As of publication, no decision has been made, and the topic remains open for community comments.

Odoo maintains several official self-hosted installation paths (apt/pip/Docker/from source); n8n is considering narrowing this to a single Docker-based method, reducing deployment flexibility for operators without container infrastructure. Odoo →
n8n
OpenTelemetry tracing for workflow and node execution

Each workflow run creates a root span with status, duration, and error, plus an optional child span for each node. Enabled with two env variables, exported to any OTLP collector (Jaeger, Tempo, Datadog, Honeycomb, Grafana Cloud) with no vendor lock-in.

Kafka does not yet have native broker-side integration with OTLP tracing - it is usually instrumented through client libraries/Kafka Connect; n8n provides tracing out of the box with two environment variables Apache Kafka →
n8n
Managed connection to MCP servers without manual client setup

n8n 2.22.0: the agent connects to some external MCP servers (Apify, Linear, Notion, and others from the official MCP registry) by selecting them from the node panel and logging in, without manually creating an MCP Client node and credential.

Lowers the entry barrier to the MCP protocol to selecting a connector from a list, removing the manual client+credential setup that was previously required even for standard MCP servers MCP →
n8n
SAP makes strategic investments in n8n, valuing it at $5.2 billion, with integration into Joule Studio

The company valuation more than doubled in less than a year, starting at $2.5 billion. Under a commercial agreement, n8n is natively embedded in Joule Studio, the agent-building environment on SAP Business AI Platform, to automate processes across SAP systems and external software from a single interface.

MuleSoft has handled integration around SAP landscapes as an ESB for decades; the partnership embeds n8n as an alternative or complementary agent orchestration layer directly into the SAP stack MuleSoft →
n8n
The n8n MCP server can create and update workflows, not just run them

The AI client through the built-in MCP server (Cloud/Enterprise/self-hosted Community) now creates new workflows and edits existing ones directly in the instance, not just executes existing ones. The intermediate representation is TypeScript, which must pass type-checking and compilation before being applied to the instance, not raw JSON. Public preview, recommended version n8n 2.18.4+.

Most MCP implementations give an agent access to a tool's data/actions; here, the MCP server itself generates and validates workflow code (TypeScript), a rare case of MCP as a code-gen tool rather than just an API bridge. MCP →

Discuss n8n News

Send via: