VitruAI + Dynamo
The VitruAI for Dynamo integration ships as a Dynamo package that adds VitruAI agent-call nodes into existing Dynamo for Revit graphs, with support for Dynamo for Revit 2.13+ on Revit 2023, 2024, 2025, and 2026. It is currently shipping with 1–3 design partners running standards-enforcement and warnings-cleanup graphs, where agents act as tools inside the graph the BIM manager already owns.
- VitruAI agent-call nodes ship as a Dynamo package that you drop into your existing library, drag onto the canvas, and wire to current Revit data-processing nodes.
- Structured results return as Dynamo-typed values — lists, element references, and parameter dictionaries that the rest of the graph consumes without manual string parsing or fragile regex steps.
- Dynamo Player compatibility means standards and warnings graphs run from Dynamo Player on project workstations that never open Dynamo, so QA/QC can scale beyond the computational design team.
Install, requirements, and what runs through the integration.
-
Install via Dynamo Package Manager
Install the VitruAI package directly from Dynamo Package Manager, then restart Dynamo so the new nodes appear in your existing node library. Pair the package with the workspace token your admin issued so VitruAI nodes can call agents such as the Studio QA/QC Agent against open Revit models. Most firms standardise the install path so every Revit workstation sees the same VitruAI nodes in shared graphs.
-
Supported Dynamo and Revit versions
VitruAI for Dynamo supports Dynamo for Revit 2.13+ running inside Revit 2023, 2024, 2025, and 2026, matching the same host range as VitruAI + Revit. Sandbox Dynamo (standalone) is supported when the machine has a valid workspace token, so power users can prototype VitruAI graphs without opening a project model. Version checks inside the package warn if a graph runs on an unsupported Dynamo or Revit build.
-
Dynamo Player compatible graphs
Graphs that use VitruAI nodes run inside Dynamo Player with no extra packaging, so project teams can execute standards or Revit warnings cleanup flows without touching the visual script. The same VitruAI package and node names appear in both Dynamo and Player, which keeps deployment simple for BIM managers. Player runs on workstations that never install Dynamo Studio, widening the audience for QA/QC tools built by the computational team.
-
Structured agent results as Dynamo-typed values
VitruAI agent-call nodes return structured outputs as native Dynamo types — lists, element references, parameter dictionaries, and booleans — instead of opaque JSON strings. That means a standards-enforcement graph can route failing elements directly into existing filter, group, and color override nodes, or pass them into the Studio QA/QC Agent for explanation. You avoid brittle string parsing and keep graphs readable for the rest of the team.
-
Outbound HTTPS only with constrained endpoints
The VitruAI Dynamo package communicates over outbound HTTPS only, to a single FQDN and documented IP range that IT can pin in firewall rules. No inbound ports or custom services are required on Revit workstations, which keeps the security review straightforward. Logs record which graphs and users called which agents, so BIM managers can audit heavy-use standards or Revit standards enforcement flows when needed.
-
Shared graphs across Dynamo and pyRevit users
Firms that already script in Python can pair VitruAI for Dynamo with the pyRevit integration so the same agents are callable from both visual graphs and Python scripts. A standards graph might call an agent to classify elements, while a pyRevit button writes the same results into parameters or issue trackers. This keeps VitruAI nodes as one more tool in a mixed Dynamo and pyRevit automation stack, not a replacement for either environment.
Dynamo integration questions from BIM managers
-
Does this replace our existing Dynamo node library?
No, VitruAI for Dynamo adds a set of agent-call nodes to the library you already maintain; it does not replace existing Revit, list, or geometry nodes. You keep ownership of graph structure, naming, and deployment, and simply drop VitruAI nodes where an agent should inspect or modify data. In practice, firms add VitruAI nodes into existing standards-enforcement and Revit standards enforcement graphs rather than rebuilding them from scratch.
-
Does it work in Dynamo Player?
Yes, graphs that include VitruAI nodes run in Dynamo Player with the same package and node names you see in the Dynamo canvas. This lets project teams execute warnings-cleanup or standards checks from Dynamo Player even if they never open Dynamo itself. Many BIM managers publish a curated Player library that calls VitruAI nodes for Revit warnings cleanup while keeping editing rights with the computational design group.
-
How does it differ from the pyRevit integration?
VitruAI for Dynamo runs inside Dynamo’s visual scripting environment, while the pyRevit integration exposes the same agents to Python scripts and custom buttons in Revit. Dynamo graphs suit users who think in node networks and want Player support; pyRevit fits teams that prefer code, source control, and scripted batch tools. Many firms run both integrations so visual graphs and scripted tools can call the same QA/QC agents against shared Revit models.
-
Will graphs that use VitruAI nodes break for users without the integration?
If a workstation does not have the VitruAI package installed, VitruAI nodes in a graph resolve as missing and that graph will not execute correctly. Most firms avoid this by deploying the package through a central Dynamo Package Manager path or Revit image so every user sees the same node set. For Dynamo Player, BIM managers usually test graphs on a clean machine to confirm that only the standard and VitruAI packages are required.
-
What does the Beta cohort look like?
The Beta cohort currently includes 1–3 design partners with active Dynamo libraries focused on standards-enforcement and warnings-cleanup graphs. These partners already run Revit 2023+ in production and have at least one BIM manager or computational designer maintaining shared graphs. Each Beta deployment ships a per-project accuracy and performance report calibrated to that firm’s pipeline, so they can see how VitruAI nodes behave in their own Revit and Dynamo environment.