denis256 notes and projects

n8n [email protected] was published on July 7, 2026, as a stable patch release for the n8n automation platform. The main fix is in core: the Code node should no longer fail only because a workflow also contains an AI tool. This release is not marked as a prerelease.

The full release notes and downloads are on the GitHub release page.

Code node workflows with AI tools

The core fix in this release is aimed at workflows that combine the Code node with an AI tool. The release note says n8n now prevents a Code node failure when a workflow contains an AI tool, tracked in #33644 and commit df12545.

For teams using n8n as a workflow glue layer, this is the kind of patch that matters more than its size suggests. Code nodes are often where teams put the small bits of JavaScript that adapt payloads, shape API responses, or bridge gaps between nodes. AI tools tend to sit in the same workflows when the automation is doing classification, extraction, routing, or generation.

The useful part here is scope. The note does not describe a new AI feature or a behavior change in Code node execution. It describes a failure condition that should no longer trip workflows just because those two pieces appear together. If your workflows mix custom Code node logic and AI tool nodes, this is the first fix to look at in [email protected].

Editor actions across node versions

The editor fix covers action generation for nodes that use a flat Action field across versions. The release note links this to #33663 and commit 246a5c8.

That sounds small, but it sits in a visible part of the product. Node actions are how users discover and select what a node can do. If action generation is wrong across node versions, the editor can become noisy or misleading even when the runtime logic behind the node is fine.

This release note is also careful about the shape of the change. It names the flat Action field and says the fix applies across versions. That points to compatibility inside the editor model rather than a broad redesign of node behavior. Operators should read this as an editor correctness patch, especially for workflows that include nodes with multiple versions or older node definitions.

Salesforce uploads and JWT auth errors

The Salesforce Node gets the most concrete integration fix in the release. [email protected] fixes document uploads and surfaces errors on JWT auth, linked from #33636 and commit 0cfc45c.

There are two practical parts here. First, document uploads should behave correctly again for Salesforce workflows. That matters for automations that attach contracts, forms, exports, or generated files to Salesforce records.

Second, JWT auth errors should be visible instead of hidden or unclear. This is boring in the right way. When JWT auth fails, operators need the actual error path quickly, because the fix might live in certificates, connected app settings, claims, clocks, or credentials. Better error surfacing shortens that loop. It does not remove the need to debug Salesforce auth, but it should make the failure less opaque.

Where to get it

• Release page: [email protected] release
• Repository: n8n-io/n8n
• Tag: [email protected]