CAD/BIM File Conversion using Local Command Line Executables - n8n Workflow

BIM and VDC Managers: Who need to automate data extraction or conversion from design files (Revit, IFC).
Construction Technologists: Seeking robust integration between low-code tools like n8n and specialized engineering applications.
Developers & Engineers: Anyone looking to leverage the n8n node structure to manage local script execution.
Automation Specialists: Interested in utilizing n8n for system-level operations and file processing.

Processing specialized file formats like CAD and BIM often requires proprietary software or specific command-line tools. This n8n workflow provides a perfect bridge, allowing the robust automation capabilities of n8n to control and manage these local system executions.

This specific n8n workflow template is designed to interface with the Data Driven Construction conversion tools (like RvtExporter.exe). By defining the paths within a simple n8n node, you can easily switch between projects or conversion executables without modifying the core system command logic. This efficient setup makes the n8n workflow highly reusable for various file processing tasks where external command-line utilities are required. Using this n8n automation, you turn a tedious manual conversion process into a reliable, single-click execution managed entirely by your n8n instance.

This automation is triggered manually and follows a simple, three-step linear process, demonstrating how to use the Execute Command n8n node effectively with local variables.

1. Manual Start: The n8n workflow begins with the Manual n8n trigger. This is designed for testing or for scenarios where the conversion needs to be initiated on demand.


2. Define Configuration (Set Node): The subsequent Set n8n node is the critical configuration point. It defines two variables: pathtoconverter (the exact location of the executable, e.g., RvtExporter.exe) and pathprojectfile (the path to the Revit or CAD file to be converted). This separation makes the overall n8n template extremely flexible.


3. Execute Conversion: The final Execute Command n8n node combines these two variables into a single system command. It calls the executable defined in pathtoconverter and passes the project file path as an argument, initiating the local file conversion process. The output of this n8n node will contain the result (or error message) of the command execution.

To deploy and run this specialized n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and import it directly into your n8n instance using the 'New' menu -> 'Import from JSON'.


2. Prerequisites: Ensure that the specific CAD/BIM conversion executable (e.g., RvtExporter.exe from the Data Driven Construction suite) is installed and accessible on the machine hosting the n8n execution environment.


3. Configure the Set n8n Node: Open the 'Set' n8n node and update the parameters:

1. Troubleshooting Note: As highlighted in the sticky note within the n8n workflow, ensure you reference the executable inside the dedicated datadrivenlibs folder if necessary to avoid path errors.


2. Execution: Save the n8n workflow and click 'Test workflow' on the Manual n8n trigger to run the automation.

When clicking ‘Test workflow’ (Manual Trigger):
Function: Serves as the starting point, acting as the manual n8n trigger to initiate the sequence.
Key Configuration: Standard manual execution setup.

Set (n8n Node):
Function: Defines necessary file paths as variables used later in the execution command. This abstracts configuration from logic, enhancing the reusability of the n8n workflow.
Key Configuration: Defines pathtoconverter and pathprojectfile using static string values representing local file system locations.

Execute Command (n8n Node):
Function: Executes the local command-line utility for file conversion using the paths provided by the previous n8n node.
* Key Configuration: The command parameter dynamically combines the variables: ="{{$json["pathtoconverter"]}}" "{{$json["pathprojectfile"]}}".