n8n Release Notes 2.40: New Microsoft Dataverse Node Explained
n8n release notes 2.40 cover a new Microsoft Dataverse core node and 32 other features, released September 15, 2026, plus what the announcement leaves unstated.
Checked against the cited sources on .
What Changed in n8n 2.40
n8n's official release notes page headlines n8n release notes 2.40, released on September 15, 2026, around two things: a brand-new Microsoft Dataverse core node, and 32 other features bundled into the same release, according to n8n's own release notes page. If your team runs workflows that touch Microsoft's business data platform, or you simply track every core node update that lands in n8n, this release is worth a close look.
The headline item is the Microsoft Dataverse core node itself: a dedicated node for reading and writing rows in a Dataverse environment, shipped as a first-party n8n node rather than a community add-on, per the same release notes.
Sources: Release notes | Changelog | n8n Docs
The New n8n Microsoft Dataverse Node: Operations and Authentication
According to n8n's 2.40 release notes, the new node supports six operations against a Dataverse environment, covering the core actions a workflow would need to manage records there.
- Create a new row
- Update an existing row
- Upsert a row (create or update)
- Delete a row
- Get a single row
- List rows
n8n's GitHub release record for 2.40.0 confirms the node under its 'Features' section, tied to a single pull request, though the commit log itself gives no further detail on credential setup beyond what the docs release notes describe. Readers tracking every n8n core node update will need to rely on n8n's documentation rather than the changelog entry for setup specifics.
Sources: Release notes | Changelog | n8n Docs, Release n8n@2.40.0 · n8n-io/n8n · GitHub
The Other 32 Features at a Glance, With One Concrete Example
Beyond the Dataverse node, n8n describes the release as including 32 other features, a headline count stated directly on the release notes page, though the page does not catalogue all 32 individually in the format reviewed here.
One example n8n's GitHub release log does spell out: the Confluence node was unhidden from the nodes panel and enabled for use as an AI Agent tool, per the 2.40.0 release entry. That single line shows the 32 features are a mixed bag of node visibility changes, AI-agent enablement and other smaller edits, not one uniform type of change.
Sources: Release notes | Changelog | n8n Docs, Release n8n@2.40.0 · n8n-io/n8n · GitHub
When n8n 2.40 Shipped and How n8n Versions Its Releases
n8n release notes 2.40 state a release date of September 15, 2026, a date confirmed both by the docs release notes and by n8n's GitHub release record for 2.40.0.
Browsing the wider n8n changelog for September 2026 shows versions arriving in quick succession: an archived release-notes page, which n8n itself marks as no longer updated, shows the stable line having already moved on to version 2.42.3 by the time that page was last captured. We use this only to illustrate that n8n ships frequently, not as current evidence about what 2.40 itself contains.
Sources: Release n8n@2.40.0 · n8n-io/n8n · GitHub, Release notes 2.x | Changelog | n8n Docs
What the n8n 2.40 Release Notes Do Not Say
The 2.40 release notes do not state which n8n editions, Community or Enterprise, the Dataverse node or the other 32 features apply to, nor whether they differ between n8n Cloud and self-hosted instances. That is simply not addressed on the page, not a gap we are filling in on the announcement's behalf.
| Topic | What the release notes say |
|---|---|
| Release date | Stated: September 15, 2026 |
| Dataverse node operations | Stated: Create, Update, Upsert, Delete, Get, List Rows |
| Edition (Community vs. Enterprise) | Not documented |
| Hosted plan (Cloud vs. self-hosted) | Not documented |
| Feature-flag status of the Dataverse node specifically | Not documented |
Elsewhere on the same release notes page, n8n notes generally that some features ship behind a feature flag readers may need to enable, and that others roll out gradually to Cloud or self-hosted instances before reaching everyone. The page does not say whether this general caveat applies to the Dataverse node or to any specific one of the 32 other features. We'd treat that silence as a reason for caution before assuming the node is already live everywhere, rather than as a confirmed rollout schedule.
Sources: Release notes | Changelog | n8n Docs
What Readers Should Do Now
The release notes themselves describe what changed, not what a team should do about it. The following is our own editorial guidance for teams deciding how to respond to this n8n release notes 2.40 update; none of it is instruction from n8n itself.
Our take: given how quickly n8n ships minor versions, a team that only skims a single release risks missing a quieter change, such as a feature-flagged rollout, that later affects their own workflows.
Background: What Microsoft Dataverse Is
For readers unfamiliar with the term, Microsoft's own product documentation describes Dataverse as a platform for securely storing and managing the data used by business applications, organized into tables of structured records that apps such as Power Apps or Dynamics 365 read and write.
Microsoft's training materials describe Dataverse further as the data foundation behind Power Platform and, increasingly, the engine behind AI agents and Copilot experiences. This background helps explain why a dedicated n8n Microsoft Dataverse node is useful: it gives workflows direct access to records that already sit at the center of many Microsoft-centric business stacks.
Sources: What is Microsoft Dataverse? - Power Apps | Microsoft Learn, Describe Microsoft Dataverse - Training | Microsoft Learn
