In a large multidisciplinary project, divide Assistant automation between one central master workflow and Actions files owned by each discipline.
The master workflow manages applications, models, publishing, and the execution context. Each discipline Actions file contains small actions that operate on the current open model. This structure lets a project reuse the same discipline automation in scheduled runs, local design work, and ad-hoc jobs on an automation computer.
Keep one Master.actions file on a dedicated automation or export computer. The project's Automation Responsible owns this file.
A typical scheduled run follows this sequence:
Master.actions
|
+-- Run common project tasks
+-- Loop through models
| +-- Open the model
| +-- Identify its discipline
| +-- Run the discipline Actions file
| +-- Save and close the model
| +-- Publish the model
+-- Run common final tasks
+-- Store the run result
+-- Send the final status
The master workflow is responsible for:
Keep model selection, application startup, and publishing in the master workflow. A discipline Actions file receives an open model and performs discipline work on that model.
Use the Loop task, Conditional task, and Run Actions file task to build this routing. Enable Share connection in the Run Actions file task so the discipline file receives the current Revit connection. Use Run only selected tasks when the master workflow must call only part of the discipline file.
Give each discipline its own Actions file:
Project Automation
|-- Master.actions
|-- Structural.actions
|-- Mechanical.actions
|-- Electrical.actions
`-- Landscape.actions
The discipline team owns and maintains its file. For example, Structural.actions might contain these actions:
01 - Update parameters
02 - Export IFC
03 - Run model checks
04 - Create coordination output
05 - Prepare discipline data
Each action must work against the current open model. It must not choose which project model to open. The caller supplies that context:
| Execution mode | Starts Revit | Opens the model | Runs the discipline logic |
|---|---|---|---|
| Scheduled | Master workflow | Master workflow | Discipline Actions file |
| Local on-demand | User | User | Discipline Actions file |
| Server ad-hoc | Submitted job | Submitted job | Discipline Actions file |
Keep the actions small. The master workflow can combine several actions for a nightly run, while an engineer can run only Export IFC during the day.
Use a schedule trigger on the automation computer to start the master workflow outside working hours.
Scheduled start
|
+-- Prepare the workspace
+-- Loop through models
| +-- Open the current model
| +-- Run the matching discipline actions
| +-- Save and close the model
| `-- Publish the model
+-- Upload results
+-- Store the run result
`-- Send a summary email
Assistant must remain running with triggers enabled. If Assistant is closed, the trigger cannot start the workflow.
Expose suitable discipline actions through Assistant Shortcuts. An engineer can then run an action against the model that is already open in Revit or Tekla.
For example, a structural ribbon panel might contain:
[ Update parameters ] [ Export IFC ] [ Run model checks ]
The Actions file remains the source of the automation. A Shortcut only provides access to an action or action group.
Do not expose every scheduled action as a Shortcut. Use Shortcuts for actions that are safe and useful while other project members work in the model.
Use a folder trigger when an engineer needs the automation computer to run a job outside the schedule.
Treat the trigger folder as a submission queue. When Assistant detects an .actions file, it reads the file and deletes the queue copy. Do not create or maintain an Actions file in the trigger folder.
Store each ad-hoc job template in a permanent project location. To submit a job, copy the template into the trigger folder:
Permanent job template
|
| copy
v
Trigger folder
|
+-- Assistant reads the job
+-- Assistant deletes the queue copy
`-- Assistant runs the job
The permanent discipline Actions file does not go into the queue. The submitted job only creates the execution context and calls that permanent file.
A local Shortcut can assume that the correct application and model are already open. An ad-hoc server job cannot make those assumptions.
For Revit, include these steps in the submitted job:
For example:
AdHoc-Structural-IFC.actions
1. Start Revit 2025
2. Open the structural model
3. Run Actions file
File: \\ProjectShare\Project\Automation\Disciplines\Structural.actions
Action: Export IFC
The queue copy is temporary, so it must not resolve dependencies relative to its own location. Use a stable full path that the automation computer can access:
\\ProjectShare\Project\Automation\Disciplines\Structural.actions
Do not use a relative path such as:
..\Disciplines\Structural.actions
Use full paths for every external file referenced by the submitted job.
Enable action-run logging on the automation computer and store .actionrun files in a shared project location. See Log action runs and View runs.
Organize the history by date so discipline teams can inspect the previous run:
Project Automation
|-- Actions
| |-- Master.actions
| `-- Disciplines
| |-- Structural.actions
| |-- MEP.actions
| `-- Electrical.actions
|-- Ad-hoc Templates
|-- Action Runs
| |-- 2026-09-21
| `-- 2026-09-22
`-- Outputs
Configure the master workflow to send a final status email after every scheduled run. Send one message after success and another after failure. If neither message arrives, the workflow may not have started.
Discipline workflows can also send a per-model notification. Use these messages when a discipline needs confirmation for each model or needs failures to reach the responsible team directly.
| Result | Recipient |
|---|---|
| Master success | Automation Responsible |
| Master failure | Automation Responsible |
| Discipline success | Optional discipline recipient |
| Discipline failure | Discipline responsible |
The Send mail task requires an Assistant Cloud login. Add Assistant Cloud to the required logins in a shared Actions file.
Classify each action by whether it reads from the model or writes to it. Broad write operations can conflict with active users through element ownership and worksharing.
Actions commonly suited to on-demand daytime use include:
Check the behavior of each action before making it available as a Shortcut.
Prefer scheduled execution outside working hours for actions that:
For a model-changing nightly run, use this controlled sequence:
Start the required Revit version
|
Open the workshared model
|
Run the discipline write operations
|
Run exports and checks
|
Save or synchronize the model
|
Close the model
|
Publish the model
Agree on the schedule and synchronization behavior with the project's Revit or BIM management team.
The Automation Responsible maintains:
Master.actions;.actionrun storage;Each discipline team maintains:
PROJECT AUTOMATION
|-- Master
| `-- Master.actions
|-- Disciplines
| |-- Structural.actions
| |-- MEP.actions
| |-- Electrical.actions
| `-- Landscape.actions
|-- Ad-hoc Templates
| |-- Structural IFC.actions
| `-- Structural Parameter Update.actions
|-- Ad-hoc Queue
| `-- Temporary submitted copies
|-- Action Runs
| `-- Dated .actionrun history
`-- Outputs
|-- IFC
|-- Reports
`-- Other deliverables
Keep Ad-hoc Templates separate from Ad-hoc Queue. Templates are permanent project files. Queue copies are temporary job requests that Assistant consumes.
Before you enable the project automation, confirm that:
.actionrun files are stored for later review;