In brief
- The Revit walkthrough focuses on running an existing plugin on Automation Service; it does not teach plugin development.
- Because user interaction is not possible in the cloud Revit environment, references to the user interface must be removed from the plugin.
- The example workflow requires changes to C# code; those without C# experience can start with the second task using the sample DeleteWalls.dll plugin.
- Requests can be sent with cURL or made using the Postman collection prepared for the walkthrough.
Autodesk Platform Services (APS) Design Automation API v3 enables workflows for creating, inspecting, and modifying Revit data in the cloud. Autodesk’s official Revit walkthrough shows how to run an existing Revit plugin in the Automation Service environment, which has no user interface. Rather than teaching plugin development, this guide focuses on preparing an existing plugin for cloud execution and following the request flow in the documentation. The documentation does not specify a particular Revit version number, hardware requirements, or pricing.
What tasks can be moved to the cloud?
Identify repetitive work. First, define which operation is frequently repeated in Revit files or needs to be applied to many models. APS documentation describes the Design Automation API as a service for offloading repetitive or large-scale workloads. Revit use cases in the documentation include creating models, inspecting model data, automatically generating reports, modifying existing models to meet company standards, and preparing documentation.
This step helps determine whether a plugin is actually suitable for automation. If an operation depends on user decisions or controls on screen, it may not be possible to move it to the cloud as is. Clarifying the expected inputs and outputs first helps keep the scope under control when preparing the plugin.
Start with an existing Revit plugin. The walkthrough does not explain how to write a plugin; it focuses only on running one on Automation Service. If you do not already have a plugin, this guide should not be treated as a standalone plugin-development manual. Autodesk points readers to the Revit Developer Center for information on plugin development.
This distinction matters: cloud execution does not replace plugin development. Do not assume that a plugin used in the office will also work in the cloud; UI dependencies and the workflow must be addressed separately. Limiting the first attempt to one clearly defined task makes it easier to see what preparation is needed.
Preparing the plugin for cloud execution
Remove user-interface dependencies. According to Autodesk, user interaction is not possible on Automation Service. Revit plugins are generally designed to interact with the user interface, so all UI references must be removed from the plugin before it can run in the cloud.
This is because, in a cloud environment, a user cannot open an on-screen window and make a selection or click a confirmation button. The operation must therefore be converted into a workflow that does not depend on intermediate decisions from a user. In the documentation, Task 1 is defined as the step for making the plugin compatible with the Automation API. Removing UI references is part of this preparation.
Assess the required code changes. Autodesk’s walkthrough requires changes to C# code in the first task. If you do not have sufficient C# experience, the documentation says you can start with Task 2 using the Automation API-ready sample plugin called
DeleteWalls.dll. The filename identifies the sample plugin; it should not be treated as a general-purpose tool for unrelated Revit tasks.Using the sample can help you follow the request steps, but it will not automatically resolve the UI dependencies or workflow logic in a plugin used in a real project. When moving on to your own plugin, review its code and functionality separately. The documentation does not provide a specific list of code changes or a conversion recipe that applies to all plugins.
Sending requests and following the workflow
Follow the walkthrough’s task sequence. The Revit walkthrough breaks down the process required to run a plugin on Automation Service. The first task is performed entirely in Visual Studio and does not send a request to APS. That is why Autodesk’s Postman collection has no group for Task 1.
This detail prevents anyone looking for the first task in Postman from assuming something is missing. The intended sequence is to prepare the plugin first, then move on to communicating with the service. Task names and request names in the documentation are matched; following those names helps clarify which request belongs to each stage.
Use Postman or cURL. Autodesk’s prepared Postman collection brings together the HTTP requests used in the walkthrough. Requests are grouped by task, and those who do not want to use Postman can follow the same walkthrough with cURL. Postman is presented as a graphical option for sending HTTP requests.
Teams that prefer to send requests manually can use cURL, while those who want a graphical interface can use the Postman collection. The important thing is to track the example request name alongside the task it belongs to. The source text does not provide a Revit version compatibility table or request parameters applicable to every project, so it would be unwise to assume values that are not in the documentation.
Run the operation in the cloud Revit environment. APS provides access through the Automation API to a cloud-based version of Revit that has no user interface. The documentation says that the Revit DB API can be accessed without installing Revit on a desktop. This enables cloud-based applications and services for creating, extracting, and modifying model data.
At this stage, check the operation the plugin is intended to perform, its inputs, and the expected results against your project requirements. This final check does not mean Autodesk provides a specific validation command; it is a project practice that can help ensure the automation is used reliably in an office workflow. The sources do not specify a detailed method for downloading results or a particular Revit version.
Impact on architecture and visualization workflows
Architecture and interior design teams with repetitive checks, data extraction, reporting, or documentation tasks in Revit models may want to consider this approach. In particular, applying the same types of operations to multiple models is a good starting point for assessing whether tasks currently performed individually on desktop are suitable for cloud automation. However, the sources do not specify any particular speed improvement or time savings.
For archviz teams, no direct rendering feature is described. The documentation focuses on running Revit plugins in the cloud and does not specify a render engine, image-quality settings, or graphics card requirements. Its use cases should therefore be considered limited to model data and Revit plugin operations. Licensing and pricing terms are also not explained here; they should be reviewed separately before moving to a cloud workflow.
Common mistakes
Moving a plugin that uses the user interface to Automation Service without making any changes. The documentation requires UI references to be removed.
Mistaking the walkthrough for a plugin-development course. It explains how to run an existing plugin.
Looking for Task 1 in the Postman collection. The first task takes place in Visual Studio and does not send an APS request.
Treating the
DeleteWalls.dllsample as a ready-made solution for every project. The source presents it as a specific sample plugin that lets users start from Task 2.Assuming Revit versions, pricing, hardware requirements, or request parameters that are not in the documentation. These topics are not specified in the source texts.
Sources
2 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and interior design offices in Turkey, APS Design Automation may be worth considering, especially for teams that repeatedly perform the same Revit operations. However, the main effort is not simply sending a request to the cloud; it is removing the plugin’s UI dependencies and checking that it produces the right results in the real workflow. It is therefore better to start with a small, clearly scoped operation.
The documentation does not explain pricing, licensing terms, Revit versions, or hardware requirements, so decisions should not be based on assumptions about cost or compatibility. The `DeleteWalls.dll` sample is also no substitute for every office’s plugin. A practical starting point is for teams to assess their existing plugin and C# expertise, then follow the official walkthrough with Postman or cURL.
Frequently asked questions
Can a Revit plugin be run in the cloud with APS Design Automation?
Yes. Autodesk’s APS Design Automation API v3 documentation includes a walkthrough for running Revit plugins on Automation Service. User interaction is not possible in the cloud environment.
What needs to be done before running a Revit plugin on Automation Service?
References to the plugin’s user interface must be removed. Autodesk’s walkthrough also includes a preparation step that requires changes to C# code.
Can Revit Automation API requests be sent with Postman?
Yes. Autodesk’s Postman collection includes the walkthrough’s HTTP requests, grouped by task. Requests can also be sent with cURL.



