Research-backed — sourced directly from the publisher, checked 2026-10-05. This is a same-day note, not a tested guide: we have read the official source and quote it directly below; we have not independently run or verified the change itself, and no price or outcome here should be taken as a TNT Review recommendation.
What changed
n8n has introduced a dedicated Microsoft Dataverse core node to manage rows in a Dataverse environment. The node supports Create, Update, Upsert, Delete, Get, and List Rows operations using OAuth2 authentication.
This is reported here because it directly affects the practical, free-first workflows this library already covers, and because it comes from the vendor’s own official channel rather than a secondhand summary. TNT Review did not produce this change and makes no claim about how well it works beyond what the source itself states.
In the source’s own words
Add Microsoft Dataverse core node : Added a new Microsoft Dataverse core node, supporting Create, Update, Upsert, Delete, Get, and List Rows operations against a Dataverse environment.
Read the original announcement for the complete, unedited context — a short quote here cannot carry every qualifier the source itself includes.
Why it matters for a free-first workflow
TNT Review’s practical library prioritises the free path first and only mentions a paid option where it is genuinely necessary, so this note exists to flag the change — it is not a recommendation to pay for anything new. If this turns out to open up a free or cheaper way to do something that previously needed a paid tool, that is exactly the kind of change this category exists to track.
If a full tutorial is warranted once this is confirmed first-hand, it will be built, tested and added to the relevant category as a complete guide, with its own downloadable example and its own test record, rather than left sitting as this short note.
What we have not checked yet
This note reflects one official source, read once, on the day above. It has not been cross-checked against a second independent source, it has not been tested end to end by TNT Review, and nothing here should be treated as a guarantee that the change behaves exactly as described for every setup.
A reader who wants to act on this today should still confirm the current detail directly from the source link above before relying on it, since a short note like this one is deliberately not a substitute for the vendor’s own complete documentation.
What happens next
TNT Review checks this same official source again as part of its next daily pass. If the detail changes, or if it turns out to matter less than it first appeared to, that will be reflected the next time this category is revisited — this note is a snapshot of one day, not a permanent page.
Who this is actually for
This note is useful to someone already working in this space who wants to know about a change the day it happens, not someone looking for a first tutorial on the topic. If that is you, the category this note sits in has longer, tested guides that start from the beginning instead.
Nothing on this page is sponsored, and TNT Review was not given early access to this change ahead of its public announcement — everything here was read from the same public source any reader can open themselves.