n8n 2.29.7 - Code Node And Salesforce Fixes

n8n 2.29.7 was published on July 7, 2026, as a small stable release for workflow operators. The main fix is in core runtime behavior: the Code node should no longer fail just because a workflow also contains an AI tool.

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

The core fix in #33644 is the item to read first if n8n is part of an ETL or web processing path. The release notes state that n8n now prevents Code node failure when a workflow contains an AI tool. That is narrow, but it matters because Code nodes often sit near the boundary between structured connectors and custom data shaping.

For operators, the risk was not an exotic feature flag. A workflow could include an AI tool and still depend on Code node logic for mapping fields, normalizing payloads, or preparing records before a write step. If that graph shape triggered a failure, the visible symptom would be a workflow error rather than a clean data contract violation.

The release notes do not describe a schema change, a new setting, or a migration task. Treat this as a runtime correctness fix around mixed workflows. If production workflows combine AI tool nodes with JavaScript transformation logic, this patch is worth testing against the same input payloads that exercise those Code nodes today.

The editor fix in #33663 covers generated actions for nodes using a flat Action field across versions. This is not presented as a workflow engine change. It is still relevant for teams that standardize workflow creation through the editor and depend on consistent node action choices.

Generated actions are part of how node capabilities become visible during workflow assembly. If action generation changes across node versions, operators can see drift between what a connector supports and what the editor exposes. That can slow down incident response when a workflow has to be patched under time pressure.

The useful detail is the shape called out in the notes: a flat Action field. That is more specific than a generic editor cleanup. It points to metadata handling for nodes where action data is not nested in a newer or richer layout. The post should not overstate it; the release does not claim a broad metadata rewrite.

The Salesforce Node fix in #33636 is the most direct data movement change in this release. The notes say document uploads are fixed, and that JWT auth errors are now surfaced. Both affect the same operational pattern: moving files or records into Salesforce without losing the reason for a failed write.

Document upload failures are usually noisy in the wrong way. A workflow can have valid upstream extraction, valid mapping, and a failing final connector call. When the target is Salesforce, that often leaves the operator checking credentials, payload size, content type, and API permissions before knowing whether the connector path itself is at fault.

Better JWT auth error visibility cuts that loop down. The release notes do not list specific error text, so there is no point inventing it here. The practical change is simpler: failed JWT authentication should now expose the auth error instead of forcing operators to infer it from a later or less useful connector failure.

For data teams, this is a small patch with a clear blast radius. It touches workflows that use Salesforce document uploads and JWT based authentication. It does not claim a broader Salesforce API refresh, bulk loading change, or credential model change.