Start with the production problem
The best automation opportunities are usually boring: repeated exports, parameter checks, sheet setup, naming cleanup, view creation, model audits, and data preparation.
Choosing the technology before defining the task often creates scripts that are clever but hard to maintain.
When each tool fits
Dynamo is effective for visual scripting, quick prototypes, and model operations that technical BIM users can inspect. pyRevit is useful when a team needs custom buttons, repeatable commands, and a more polished Revit interface. The Revit API is appropriate when the workflow needs deeper control, stronger validation, or more formal software development.
In all cases, the automation should respect the modeling standard, not bypass it.
- Use Dynamo to test and document logic quickly
- Use pyRevit for deployable production tools
- Use Revit API when the workflow requires custom development depth
- Document inputs, outputs, limits, and maintenance responsibility
Automation is an operating decision
A useful tool changes how the team works. That means documentation, ownership, enablement, and version control matter as much as the script itself.
Horizun's automation direction is tied to BIM production reality: tools should reduce friction while preserving technical control.