n8n 2.47.0 ships bug fixes across AI Agent, queues and source control
n8n 2.47.0, published November 3, 2026, is a bug-fix release covering AI Agent, queues, API exports and source control.
n8n published version 2.47.0 on November 3, 2026. The release notes list bug fixes rather than new features, and they touch several parts of the workflow automation platform.
On the AI side, the AI Agent node now points its deprecated agent type callout to an action that works. The AI builder also received several fixes: instance admins are now included in team self-healing reviews, self-healing chats open in the result project, and the Assistant chat title updates when a user builds a new agent. On the core side, new queue jobs go to one idle worker in turn, and durable system tasks export their stored last success on every main instance. Source control initialization can now run concurrently without the same problems.
Other changes cover API package export paths and package imports, redaction of MCP workflow run errors, project scopes for folder lists, and auto-deactivation, which now counts unsaved crashed executions. Several interface details were also cleaned up, including logs panel header styling and the data table storage limit banner copy.
Why it matters
Fixes to job distribution, crash counting and auto-deactivation affect whether automations run as expected. Project scope and redaction changes matter for teams that share workflows and run logs across projects. The AI builder fixes also show continued work on n8n’s AI features.
What to do
Teams running n8n should read the full release notes and test the update in a staging environment before rolling it out to production. Anyone using AI Agent nodes, MCP runs or source control should recheck those workflows after upgrading. Confirm version details and any upgrade steps on the vendor’s site.
In this story
Compare the tools in this story
The Stack Brief
Get the weekly brief
One email a week: SaaS pricing changes, launches worth knowing about, and one comparison you can act on.

Comments
Join the discussion with your GitHub account. Be civil, stay on topic.