Revit 2027.3 adds an Autodesk Assistant capability that can create and modify Dynamo graphs from plain‑language prompts. To use it safely, work on a test copy, switch Dynamo to Manual before you ask for a graph, generate a read‑only audit first, and only consider a separate rename graph after team approval of the audited results.
What changed for Revit AI in version 2027.3?
These release details were checked on November 4, 2026.
• Assistant can now build and edit Dynamo graphs from natural language, not just suggest steps. It requires network access, can use packages already installed, and won’t install or update packages. Python is added only if you explicitly ask. Autodesk notes the Assistant in Revit has exited Tech Preview; Public Revit MCP preview status is separate (Autodesk support). No separate Dynamo MCP install is required to use this feature.
• Revit 2027.3 lists Dynamo 4.2.1 with Autodesk Assistant and Dynamo MCP; “2027” is a product version label, not a calendar year (Autodesk help).
• A graph only changes the model when it runs. Dynamo’s Automatic mode can re‑run on edits; set Manual and use a test model before you request or revise a generated graph (Dynamo Primer).
How to create a Dynamo graph with Autodesk Assistant
Begin with a small test model and a task whose expected output you can inspect. The following sequence is a proposed review procedure.
• Before anything else, make a disposable test copy of the model (or a small detached file) and open it.
• Open Dynamo and switch execution to Manual. Keep it in Manual throughout drafting and review.
• Open the Assistant and request a read‑only graph. State explicitly that the graph must not modify elements.
• Describe scope precisely: for this article’s example, “audit Views but exclude view templates and schedules.”
• Ask for clear grouping, labels, and comments so reviewers can understand what each block collects, calculates, and outputs.
• If your environment has unknown add‑ins, ask the Assistant to avoid non‑core packages. If you do not want scripting, specify “no Python.”
• Save the .dyn with a name that marks it as read‑only (for example, “ViewName_Audit_readonly_v01”).
When the draft appears, pause. Do not click Run until you verify the graph contains only collection, comparison, and reporting logic—no nodes or code that write, create, delete, or rename anything. If any custom nodes or Python appear, stop and peer‑review them before proceeding.
Write a Revit automation prompt with a reviewable output
Define the naming rule and the report before requesting nodes. “Clean up view names” leaves the assistant to invent the standard. A supplied prefix mapping makes the proposed output checkable.
For this hypothetical exercise, use three rules: preserve names beginning with OFFICE-; replace a leading LEGACY_ with OFFICE-; prepend OFFICE- to other names. The rest of each name remains unchanged. These are example office rules, not Revit's naming restrictions.
A read-only request could say: “Audit views except templates and schedules using the supplied prefix rules. Return the current name, element identifier, and proposed name. Flag a proposed name that matches another existing view name or another proposed name. Compare against the full relevant name set, including views excluded from renaming. Do not modify the model. Use only reviewed dependencies and clearly label the collection, comparison, and reporting logic.”
Give the actual prefix values as inputs and ask for unresolved cases to be reported. Do not ask the graph to fix conflicts by silently appending numbers. Reviewers need to see the conflicts before deciding how to name those views.
For background that helps you inspect the generated graph, see Getting Started with Dynamo.
Example: build a view-name audit before a rename graph
The following rows illustrate the requested report in a test model. They are fictional examples, not results from a live project.
• Already compliant: ID 412345 has OFFICE-Level 01 - Floor Plan. The proposal preserves it. Its own unchanged name does not count as a collision.
• Legacy prefix: ID 412678 has LEGACY_Level 02 - Ceiling Plan. The proposal is OFFICE-Level 02 - Ceiling Plan, provided no other current or proposed name conflicts.
• Conflict: ID 413002 has Level 03 - RCP. The proposal is OFFICE-Level 03 - RCP, but another view already uses that name. The report flags the row for a naming decision.
Also check proposed names against one another. Two different source names can map to the same output even when that output does not yet exist. A report checking only the existing names would miss that conflict.
Use the identifiers to reopen the exact views and compare the report with the model. Check an unchanged row, a proposed change, and a conflict. Verify excluded views separately so a filter that accidentally drops the wrong category does not appear to have succeeded merely because its remaining rows look correct.
A later rename also needs a sheet-title review. When “Title on Sheet” is blank, Revit uses the View Name for the displayed title. Renaming the view can therefore change its printed title even without writing the Title on Sheet field. See Revit view properties. Record affected placed views and their title behavior for approval; this audit should not populate or change those fields.
Inspect generated Dynamo nodes and test the result
Inspect the graph before its first run. Check that collection and comparison logic are actually read-only, including any custom nodes or code. A group label saying “Audit” and a filename ending in “readonly” do not establish what the graph executes. If a dependency is unfamiliar, have someone who can inspect it review it before proceeding.
Confirm the execution mode yourself. A prompt requesting Manual mode is not a substitute for setting it in Dynamo. Do not add write nodes behind an assumed Boolean safety switch; keep this graph limited to reporting. Any later rename workflow should be a separate reviewed task.
After the test run, compare the result with the small known cases. Record omissions, incorrect proposals, false collision flags, and unresolved dependencies. An apparently reasonable count does not establish exact membership or correct values. Preserve the reviewed graph and its input rules with the comparison evidence.
For the broader release context, see Revit 2027 AI Review. If your intended task extends across Revit, AutoCAD, and project files, ArchiLabs Desktop is another workflow to evaluate against the same explicit inputs and expected outputs.
Start with the audit and resolve its findings. A rename graph becomes a useful next task only after the naming decisions and sheet-title effects are understood.
Learn how to get started with Dynamo in Revit, and discover why ArchiLabs Studio Mode — a standalone, Python-first parametric CAD platform — is the next evolution beyond visual scripting.
Honest review of Revit 2027 AI: placement, docs, generative design, clashes, Forma links—what saves time, what’s half‑baked, and gaps.