CAD2DATA: Batch Converter (Revit/IFC/DWG/DGN → XLSX/DAE) Batch-convert CAD/BIM files to analysis-ready XLSX and optional DAE with automatic verification and a clean HTML report. Runs locally via RvtExporter.exe and PowerShell on Windows. Supports configurable export modes — basic (309 categories), standard (724), and complete (1209) — plus optional outputs such as bounding boxes, Revit schedules, and PDF drawings. What it does - Scans a source folder (optionally including subfolders) for .rvt, .ifc, .dwg, or .dgn. - For each file, runs: RvtExporter.exe [input] [output.xlsx] [output.dae] [options]. - Verifies outputs (existence + size) and aggregates results. - Generates a summary HTML report and opens it automatically on completion. Converter options - Export modes: basic | standard | complete | custom - Flags: bbox (BoundingBox to XLSX), schedule (Revit schedules), sheets2pdf (Sheets → PDF) - Disable: -no-xlsx, -no-collada - Custom files: [<output file>] and [<category file>] (used with custom) Examples - basic bbox — minimal export + BoundingBox - complete schedule sheets2pdf — full export + schedules + PDFs - standard -no-collada — XLSX only (skip DAE) Prerequisites - Windows host (PowerShell + local executable). - DDC Revit toolkit installed: C:\DDCConverterRevit\datadrivenlibs\RvtExporter.exe - Read access to the source folder and write access to the output folder. How to use 1. Import this JSON workflow into n8n. 2. Open Set Configuration Parameters and set: - converterpath: C:\DDCConverterRevit\datadrivenlibs\RvtExporter.exe - sourcefolder: folder with your projects - outputfolder: folder for results - includesubfolders: true / false - fileextension: .rvt | .ifc | .dwg | .dgn - options: see Converter options 3. Run Manual Trigger. 4. The workflow discovers files → runs conversions → verifies outputs → writes and opens the HTML report. Outputs - ext.xlsx — tabular data per input file. - ext.dae — lightweight 3D (if not disabled with -no-collada). - CADConversionReportYYYY-MM-DDHH-MM-SS.html — summary with: - success rate and progress - per-file and total processing time - input/output sizes and file paths Notes & tips - Uses PowerShell Get-ChildItem for discovery and cmd /c start to open the report. - With -no-collada, success/verification is XLSX-only (DAE is skipped). - Prefer ASCII paths and ensure write permissions in the output folder. Categories Data Extraction · Files & Storage · ETL · CAD/BIM Tags cad-bim, revit, ifc, dwg, dgn, converter, batch, xlsx, dae, qto Author DataDrivenConstruction.io Author DataDrivenConstruction.io info@datadrivenconstruction.io Consulting and Training We work with leading construction, engineering, consulting agencies and technology firms around the world to help them implement open data principles, automate CAD/BIM processing and build robust ETL pipelines. If you would like to test this solution with your own data, or are interested in adapting the workflow to real project tasks, feel free to contact us. Docs & Issues: Full Readme on GitHub
