n8n shipped 2.43.0 on October 6, 2026, and the changelog reads like a production-hardening checklist rather than a feature launch. The marquee fix is a simple one: n8n now blocks you from publishing a workflow that has unconnected required node inputs (commit 5e28ff8, tracked as #37265). Around it, the release applies policy checks to CLI commands, extends MCP availability rules to error workflows, deduplicates agent message deliveries, and fixes agent session handling on SQLite. The pattern is unmistakable — n8n is spending this release cycle on making agents fail less often, not do more things.
In this post: what each of the important 2.43.0 changes actually does for you, why the publishing guardrail is the headline, and the upgrade path if you’re self-hosting.
The headline: n8n stops you from publishing broken workflows
The most impactful single change is core: Block publishing workflows with unconnected required node inputs. Before 2.43.0, you could publish (activate) a workflow where a required input of a node was left dangling — say you dragged in an Agent node, connected the model, but never wired the chat trigger. The workflow would then run in production and fail silently, or worse, fire half-built automations against real APIs.
Now the editor refuses to publish until required inputs are connected. This matters more than it looks:
- For agent workflows, “required inputs” includes the tool connections, memory, and model sub-nodes that the Agent node depends on. Agents are exactly the workflows most likely to be published half-wired because they have the most connections.
- For teams, it kills a whole class of “it worked in testing” incidents where a dev published a draft during iteration and forgot.
- For automated publishing (CI/CD pipelines that activate workflows via the API or CLI), this pairs with the new CLI policy checks below — the same guardrail logic is being applied everywhere publishing happens.
The honest limitation: this only catches structurally unconnected required inputs. It will not catch a connected-but-misconfigured node, a wrong credential, or a prompt that hallucinates. Structural guardrails shrink the failure surface; they don’t eliminate testing.
Policy checks now apply to the CLI too
Two related changes extend n8n’s guardrail logic beyond the editor UI:
core: Apply policy checks to CLI import and execute commands (#39714)— organizations that define policies (restrictions on node usage, credentials, etc.) now get those same policies enforced when workflows are imported or executed through the n8n CLI. Before this, a policy that blocked a risky node in the editor could be bypassed by importing the same workflow from the command line. That’s a real hole, and it’s now closed.core: Apply MCP availability rules to error workflow settings (#39885)— MCP, or Model Context Protocol, is the standard way AI tools expose themselves to models. n8n checks which MCP features are available to an instance; this change makes those same availability rules apply to error workflows (the workflows that run when another workflow fails). Your failure handlers get the same tooling guarantees as your main workflows.
Together with the publishing block, these three changes form a coherent theme: guardrails that previously only existed in the editor now follow the workflow everywhere — CLI, error paths, and publishing.
Agent sessions get more reliable
The Agent node received several reliability fixes that matter if you run agents in production:
core: Deduplicate agent message deliveries (#39794)— agent messages were being delivered more than once in some paths. If your agent talks to Slack or a webhook, duplicate deliveries meant duplicate replies. That’s the kind of bug that erodes user trust in an agent fast.core: Correct Agent session pagination on SQLite (#39802)— if you self-host n8n with SQLite (the default for small Docker/npm installs), agent session history pagination was wrong, meaning sessions could show missing or duplicated messages. Fixed.core: Connect Slack Agent channels through managed setup in MCP (#39776)— wiring Slack channels to the Slack Agent node now goes through n8n’s managed MCP setup, which is the path n8n wants you on for agent-to-channel integrations.Agent Node: Remove outdated tutorial tip callout (#35505)andcore: Apply removed fields when the Agent Builder patches agent config (#40122)— the AI-assisted agent builder now handles deprecated fields correctly when patching agent configs, and a stale tutorial tip is gone.
Also relevant: ai-builder: Treat a blank folder path as no folder in the build tool (#40116) — a small paper-cut fix for the AI workflow builder.
Azure OpenAI Responses-only deployments now work
Azure OpenAI Chat Model Node: Support Responses-only deployments (#39403) — Azure OpenAI lets enterprises create deployments that only expose the Responses API (OpenAI’s newer unified API surface) rather than the legacy Chat Completions API. n8n’s Azure OpenAI node previously couldn’t talk to these. If your organization standardized on Responses API deployments — common in Azure-centric enterprises — your n8n agents can now use them directly instead of routing through a generic HTTP node.
What I didn’t verify: the release-notes aggregators also list expanded support for Databricks, Google Calendar, and Supabase nodes in this release. The official changelog excerpt I reviewed in detail didn’t surface the individual commits for those, so treat that list as plausible-but-unconfirmed until you read the full notes yourself.
Shutdown and multi-instance behavior gets safer
Two changes target the least glamorous part of production: shutting down cleanly.
core: Cap pending task request timeouts to the shutdown deadline (#40136)— when n8n shuts down, pending task-runner requests could hang past the deadline. Timeouts are now capped so shutdown actually completes. This matters for containerized deploys (Docker, Kubernetes) where the orchestrator kills you after the grace period whether you’re done or not.core: Keep floating entitlements attached when a multi-main instance shuts down (#39713)— in multi-main setups (n8n’s high-availability mode), license entitlements could detach during shutdown, causing entitlement checks to fail on restart. Fixed.
Plus editor quality-of-life: pasted nodes now center in the canvas viewport (#39995), the From AI button aligns with parameter inputs (#40152), and the workflow SDK group layout for AI subtrees and sticky notes improved (#39981).
API changes for programmatic teams
Three API-side fixes are worth knowing if you manage n8n programmatically:
API: Let global members grant variable scopes to API keys (#40064)— continuing the permission tightening started in 2.41.7, global members can now grant variable scopes to API keys, giving finer control over what API credentials can touch.API: Emit valid schemas for untyped values in the Public API spec (#39884)— the generated API spec no longer emits invalid schemas for untyped values, which fixes broken codegen for some API clients.core: Generate missing workflow IDs in the import:workflow command (#40011)— importing workflows via CLI no longer chokes on missing IDs.
Should you upgrade?
If you’re on the 2.4x line, 2.43.0 is a no-regrets upgrade: it’s a bug-fix release with no breaking changes, and the publishing guardrail alone is worth it. If you’re self-hosting, the upgrade is the same drill as always:
# Docker (recommended path)
docker pull n8nio/n8n:2.43.0
# then recreate your container against your existing data volume
# npm
npm install -g [email protected]Two precautions, as always: back up your n8n data first (database + ~/.n8n encryption key if you use npm), and if you’re several versions behind, skim the breaking-change notes — the October 2026 security update covered the CVE-driven releases that may have forced intermediate jumps. Running our n8n security advisory triage template against this release is a quick way to decide priority across your fleet.
What I didn’t test: I did not run the upgrade myself — the changes above are from the published changelog, not from my own instance. The guardrails are described from the release notes, so if your publishing flow goes through a custom script, test the new block in staging before it surprises your CI.
FAQ
Does n8n 2.43.0 contain security fixes?
The published 2.43.0 changelog I reviewed lists no CVEs or security advisories — it’s a bug-fix and hardening release. If you haven’t applied the October security patches yet (see the October 2026 security update), do that first; 2.43.0 includes all prior 2.x patches by virtue of being the latest point release.
Will the publishing block break my CI/CD pipeline?
It will only block publishing if your workflows have unconnected required inputs — which is precisely the case that produces broken production runs. If your pipeline publishes workflows generated by the AI builder, run one publish in staging first to confirm everything is wired. This is a feature, not a regression, but it can surface latent wiring bugs in workflows that previously published silently.
Is 2.43.0 related to the 2.42.x line?
Yes — 2.43.0 is the next release after the 2.42.x beta line we covered when 2.41.4 and the 2.42 beta shipped. The 2.42 series has stabilized into 2.43.0, so if you were tracking beta for the AI Assistant and Agent work, this is your off-ramp onto a stable-ish line.
Key Takeaways
- n8n 2.43.0 is a guardrails release, not a feature release: the headline change blocks publishing workflows with unconnected required node inputs.
- Policy checks now apply to CLI import/execute and MCP availability rules reach error workflows — guardrails follow your workflows everywhere, not just the editor.
- Agent reliability fixes: deduplicated message deliveries, corrected SQLite session pagination, and Slack Agent via managed MCP setup.
- Azure OpenAI Responses-only deployments are now supported in the Azure OpenAI node — relevant for Azure-standardized enterprises.
- Upgrade is low-risk if you’re already on 2.x; back up first, and use the security advisory triage template to prioritize across a fleet.
The bigger story: n8n is quietly rebuilding itself around production agents, one guardrail at a time. How n8n’s AI Assistant and Agents fit together is the right context piece if you want to see where this hardening trend points next.
Images: Pexels