n8n 2.45 announcement: changes and limits for teams
Read the n8n 2.45 announcement for integration changes, agent publishing updates and team review features, with clear limits on availability and dates.
Checked against the n8n documentation on .
The n8n 2.45 announcement and its release date
The n8n 2.45 announcement is recorded in the official release notes with a release date of October 20, 2026. It covers integration versions, agent publishing, AI run visibility and team review tools. The entry does not separately state an announcement publication date, so October 20 should be described as the release date.
The changes affect users of the specific nodes and interfaces described below. The announcement does not establish edition-specific eligibility, hosted-plan coverage or universal availability. We think teams should read this as a feature-by-feature review rather than assume every change applies to their setup.
Sources: Release notes
n8n 2.45 changes for integrations
The integration changes distinguish newly added nodes from existing workflows. This table summarizes the behavior stated in the n8n 2.45 release notes.
| Area | New behavior | Existing workflows |
|---|---|---|
| Monday.com | New nodes default to V2 with resource locators | Remain on V1 |
| Monday.com resources | V2 has V1 resource parity and fixes Column creation with a blank Column ID | Remain on V1 |
| Kafka version | New nodes and triggers default to V2 using librdkafka | Retain saved versions |
| Kafka compression | V2 adds Snappy, LZ4 and Zstd support | Retain saved versions |
| Kafka V2 output | Producers emit one item per input record | Retain saved versions |
| Kafka V2 Acks | Maps to all in-sync replicas | Retain saved versions |
For Azure OpenAI Chat Model users in n8n 2.45, Microsoft Foundry API Key and Entra ID credentials gain an optional Project field when Endpoint Type is Microsoft Foundry. Deployment listing uses the credential project when the node Project is empty; a populated node Project takes precedence.
Our suggested review is to check downstream Kafka output handling and the intended Foundry Project selection before adopting those changes. The announcement does not provide a migration procedure for existing Kafka workflows.
Sources: Release notes
Agent publishing and AI feedback
For teams publishing agents, n8n 2.45 adds a confirmation explaining that later changes require republishing. Unpublished workflow tools appear with publication links and block agent publication. The announcement does not supply a broader agent deployment or rollback procedure.
For users inspecting AI runs, the AI log header shows the answering model in Rendered and JSON views when run data contains a model name. That model can differ from the node’s configured model. In Agent builder, Settings refreshes monthly budget usage after a turn finishes; if refresh fails, it keeps the last known value. The sub-agent selector also gains each agent’s personalized icon and gradient.
Text Classifier users can optionally include the category, its model confidence score and a category-score map. In n8n 2.45, the option defaults off and preserves existing output when disabled, without a node version bump. These scores do not establish classification accuracy or calibrated probabilities.
In our view, publication state deserves a place in a team’s change review, while confidence output deserves caution before anyone treats it as a quality verdict.
Sources: Release notes
Migration notifications and workflow reviews
For admins reviewing migration rules, the n8n 2.45 announcement adds individual and bulk owner-email notifications. Individual notifications require configured SMTP and an owner email. Bulk notifications require SMTP and the breakingChanges:migrate scope. Notified findings still need resolution; skipped bulk rows produce a warning explaining why they were skipped.
For teams reviewing multiple workflows in the Inbox, n8n 2.45 lists each workflow’s name and pinned version in a collapsible item. Only one item opens and renders its diff at a time, and selection persists between Activity and Changes. The announcement supplies no performance benchmark.
Sources: Release notes
What to review before using the update
The n8n 2.45 announcement describes changed behavior rather than a complete upgrade procedure. Deployment commands and troubleshooting instructions are not provided here. The checklist below is our editorial suggestion for reviewing the n8n 2.45 update, not an action plan issued by n8n.
Sources: Release notes
