Batch CAD/BIM File Converter with Data Extraction and HTML Reporting - n8n Workflow

Use this comprehensive n8n workflow template to automate the batch conversion of CAD/BIM files (RVT, IFC, DWG, DGN) into structured XLSX data and DAE 3D models. Features file validation, custom scripting, and automated HTML reporting via an n8n node pipeline.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?


  • BIM Managers and CAD Professionals looking to automate weekly data extraction.

  • Data Analysts requiring structured property data from engineering models (RVT, IFC) for BI tools.

  • AEC (Architecture, Engineering, Construction) firms needing robust, validated conversion n8n templates.

  • Users running self-hosted n8n instances on Windows environments (due to PowerShell and external .exe reliance).

Overview

Manual conversion of large batches of CAD and BIM files is time-consuming and prone to error. This sophisticated n8n workflow solves this by providing a fully automated, customizable pipeline. It leverages the power of n8n to orchestrate complex operations, including file discovery via PowerShell, execution of an external conversion tool (RvtExporter.exe), per-file performance monitoring, and comprehensive output validation. The final step generates a detailed, professional HTML report summarizing success rates, file sizes, and processing times, making this n8n template invaluable for quality control and reporting in technical fields.

How it Works

This high-fidelity n8n workflow operates in seven distinct groups:


  1. Initialization (Trigger & Configuration): The process starts with a Manual n8n trigger or Schedule n8n trigger. A Code n8n node captures the pipeline start time. The Set Configuration Parameters n8n node defines critical variables like the converter path, source folder, output folder, and file extension (e.g., .rvt).

  2. File Discovery: The workflow uses an Execute Command n8n node leveraging PowerShell to scan the configured sourcefolder and list all files matching the specified extension. A subsequent Code n8n node processes this output, cleaning the paths and formatting them for batch processing.

  3. File Existence Check: An If n8n node verifies if any files were found. If No Files Found, the process ends gracefully with a warning message. If files exist, the workflow continues by splitting the list into individual items, enabling parallel processing, and ensuring the outputfolder is created.

  4. Conversion Execution: For each individual file item, the Capture Start Time Code n8n node records the conversion start time. The Execute Conversion Command n8n node runs the external conversion tool, passing the input path, expected XLSX output path, DAE output path, and any configured options. Another Code n8n node calculates the exact processing time per file.

  5. Validation: The conversion results are merged and passed to the Verify Output Files Execute Command n8n node, which uses PowerShell to check if the expected XLSX and DAE output files exist and measures their size in bytes. The Complete File Verification Code n8n node processes this data to assign a final success/failure status based on configured criteria.

  6. Reporting: The Generate HTML Report Code n8n node aggregates all individual file results, calculates overall metrics (success rate, total time, total size), and generates a beautifully styled HTML report. This report is then converted to binary data and saved using the Write Binary File n8n node to the specified output directory.

  7. Finalization: The n8n workflow concludes by using an Execute Command n8n node to automatically open the generated HTML report in the local browser and displays a final completion notice, summarizing the run details.

Installation Guide

To deploy and use this powerful n8n workflow, follow these steps:


  1. Import the n8n Workflow: Copy the provided JSON code and import it into your n8n instance via the 'Workflows' menu, selecting 'New' -> 'Import from JSON'.

  2. Install Prerequisites: This workflow requires an external conversion executable (RvtExporter.exe) and relies on native Windows commands (PowerShell, cmd). Ensure your n8n host environment has the necessary executables installed and accessible.

  3. Configure Parameters: Locate the Set Configuration Parameters1 n8n node (Group 1, highlighted in yellow).

- converterpath: Set the exact absolute path to your RvtExporter.exe file.
- source
folder: Define the folder containing your source CAD/BIM files (e.g., .rvt).
- outputfolder: Define where the generated XLSX, DAE, and HTML report files should be saved.
- file
extension: Specify the target file extension (e.g., .rvt, .ifc, .dwg).
- options: Configure any conversion flags (e.g., basic schedule -no-collada). Refer to the Sticky Notes within the n8n template for option details.

  1. Execution: Once configured, click the Manual Trigger n8n trigger and press 'Execute Workflow' to test the conversion pipeline.

Node Details

Manual Trigger / Schedule Trigger: The starting point of this n8n workflow, allowing for immediate execution or scheduling of batch conversions.
Set Configuration Parameters1 (Set n8n node): Crucial for defining all conversion environment variables (paths, extensions, options). The sticky notes emphasize that only this n8n node needs modification for setup.
Execute Command (Find CAD Files1): Uses the dynamic PowerShell command Get-ChildItem -Filter '{{ $json.fileextension }}' to reliably list all target file paths on the Windows file system.
Process File List1 (Code n8n node): Cleans the raw PowerShell output, extracts file names, and generates the exact expected output file paths (.xlsx and .dae) for each file, preparing the data structure for the batch conversion.
Execute Conversion1 (Execute Command n8n node): The core execution step. It dynamically constructs and runs the RvtExporter.exe command using data passed through the n8n workflow item, allowing for parallel execution of conversions.
Complete File Verification1 (Code n8n node): Performs complex verification logic. It parses the results from the Verify Output Files Command n8n node (PowerShell file checks) to determine if conversion was a success based on file existence and non-zero size for both XLSX and DAE outputs.
Generate HTML Report1 (Code n8n node): This highly customized n8n node compiles all metrics (start/end times, success rates, file sizes) across the entire batch into a structured, professional HTML document, showcasing the report generation capability of this n8n template.
Save HTML File1 (Write Binary File n8n node): Saves the generated HTML report content (passed as binary data) to the specified file path (fullpath), completing the documentation phase of the n8n workflow.
Open HTML Report1 (Execute Command n8n node): Uses a final system command (cmd /c start) to automatically open the generated report file, ensuring immediate review of conversion results.

Related n8n Workflows

Free

Nodes: 17 Nodes
Updated: December 26 2025
View all
Created by

Founder DataDrivenConstruction.io | AEC Tech Consultant & Automation Expert | Bridging Software and Construction

Featured*