n8n published [email protected] on July 20, 2026. The main correction restores AI Agent visibility for tools connected through HITL tools, while the editor now cleans up invalid workflow groups during save. This is a regular release, not a prerelease.
The full release notes and downloads are on the GitHub release page.
AI Agent tool visibility through HITL ¶
The core fix addresses issue 34435. Before this patch, an AI Agent could fail to see tools connected through HITL tools. The release note scopes the defect to tool visibility. It does not claim changes to model selection, prompts, credentials, or the implementation of the connected tools.
That distinction matters when validating an automation. A successful direct tool connection does not cover the affected path. Tests should use the same HITL connection structure as production, confirm that the agent can see the expected tool, and then run the normal tool call with representative input. This checks the corrected discovery path without turning a narrow patch into a general AI regression exercise.
The linked commit c9bee5e is the specific source change cited by the release. Operators who review patches before deployment can use that commit as the boundary for this fix. The notes do not mention a new setting or a migration step.
Invalid workflow groups are cleaned up on save ¶
The editor fix addresses issue 34514. When a workflow contains an invalid group, the editor now ungroups it automatically during save. Cleanup therefore happens at the point where the edited workflow is persisted, rather than depending on a user to notice and repair the invalid grouping first.
For platform teams, the useful test is a save and reload cycle. Open an affected workflow, save it, reload it, and inspect the resulting group structure before promoting the workflow. The release notes describe an editor correction, so they do not establish any broader change to node execution order, data mapping, or valid group behavior.
The release links this behavior to commit bbd15de. That commit is the relevant review point for teams that keep workflow definitions under change control or compare saved definitions during deployment.
Patch scope and rollout checks ¶
This patch contains two documented bug fixes. The notes do not list a breaking change, schema migration, new CLI flag, new configuration key, or credential format change. That keeps the documented upgrade surface narrow, but it does not remove the need to test workflows that depend on either corrected path.
Prioritize the release when production automations combine AI Agents with HITL connected tools, or when editors handle grouped workflow layouts. A focused canary should cover tool visibility, a representative tool call, workflow save, workflow reload, and the resulting group structure. For installations that use neither feature, the release notes provide no separate execution engine, queue, webhook, or database change to evaluate.
For critical workflows, retain the currently deployed artifact and export the relevant workflow definitions before rollout. The notes provide no specific rollback procedure. Existing artifact retention and workflow backup procedures are therefore the practical recovery path if local validation exposes an unexpected regression.