n8n 3.1.0 Ships a Round of Bug Fixes Across AI Builder, API and Queues
n8n 3.1.0 is a fix-focused release touching AI Builder, the API, queues and project scopes, so teams running n8n should review it.
n8n published version 3.1.0 on November 3, 2026. The release is made up mostly of bug fixes, according to the changelog on GitHub. The changes span the AI Builder, the AI Agent node, the API, the logs panel and project scopes.
On the AI side, the AI Agent node’s deprecated agent type callout now points to an action that works. AI Builder self-healing reviews now include instance admins, and self-healing chats open in the result project. The Assistant chat title also updates when a user builds a new agent.
Several fixes address security and infrastructure. Default blocked IP ranges for the outbound request guard were expanded, and execution redaction now applies to MCP workflow run errors. Project scopes now apply to folder list queries. Queue jobs are handed to one idle worker in turn, and a misconfigured S3 binary data mode is caught at boot. Unsaved crashed executions now count toward auto-deactivation.
Why it matters
Changes to request guards, error redaction and project scoping affect security and access boundaries. Teams running n8n in production should not dismiss a point release as cosmetic. Queue and boot-time changes can also affect how workflows behave under load.
What to do
Check the release notes on GitHub and see whether your setup uses the AI Agent node, queues, S3 binary data or outbound requests. Test the upgrade in a staging environment before rolling it out to production. Confirm exact behavior changes and upgrade steps on n8n’s official documentation rather than relying on this summary.
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.