ETL: Extract and Parse Revit Model Data to Structured Excel

Convert a **Revit model** to **Excel** and parse it into structured items ready for downstream EL. This minimal template runs a local `RvtExporter.exe`, checks success, derives the expected `*_rvt.xlsx` filename, reads it from disk, and parses it to data items in n8n. ## What it does 1. **Setup**: define `path_to_revit_converter` and `revit_file`. 2. **Run converter**: execute `RvtExporter.exe <converter> <revit_file>` (writes `*_rvt.xlsx` next to the RV). 3. **Check success**: branch on converter error output. 4. **Read Excel**: compute `<revit_file> *_rvt.xlsx` and read it from disk. 5. **Parse**: convert the workbook into structured items (rows → items). ## Prerequisites - **Windows** host (local executable and filesystem paths). - DDC Revit toolkit installed: `C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe`. - A local `.rvt` you can read; the converter will write `*_rvt.xlsx` next to it. ## How to use 1. **Import** this JSON into n8n. 2. Open **“Setup - Define file paths”** and set: - `path_to_revit_converter`: `C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe` - `revit_file`: e.g., `C:\\Sample_Projects\\your_project.rvt` 3. Run **Manual trigger**. 4. On success, the flow will read `*_rvt.xlsx` and emit parsed items. ## Outputs - On disk: `<YourProject>_rvt.xlsx` (created by the converter). - In n8n: parsed rows as items, ready for **Transform**/**Load** phases. ## Notes & tips - If your converter writes the Excel to a **different folder/file name**, update the “**Success - Create Excel filename**” node to point to the actual path. - Ensure write permissions in the project folder and avoid non-ASCII characters in paths when possible. - This template is purposefully minimal (Extract-only). Chain it with your own **Transform**/**Load** steps. ## Categories Data Extraction Files & Storage EL CAD/BIM ## Tags `cad-bim`, `revit`, `ifc`, `dwg`, `extract`, `xlsx`, `etl` ## Author [DataDrivenConstruction.io](https://DataDrivenConstruction.io) [info@datadrivenconstruction.io](mailto: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 EL 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](https://github.com/datadrivenconstruction/cad2data-Revit-IFC-DWG-DGN-pipeline-with-conversion-validation-qto)

n8n

Convert a Revit model to Excel and parse it into structured items ready for downstream EL. This minimal template runs a local RvtExporter.exe, checks success, derives the expected *_rvt.xlsx filename, reads it from disk, and parses it to data items in n8n.

What it does

  1. Setup: define path_to_revit_converter and revit_file.
  2. Run converter: execute RvtExporter.exe <converter> <revit_file> (writes *_rvt.xlsx next to the RV).
  3. Check success: branch on converter error output.
  4. Read Excel: compute <revit_file> *_rvt.xlsx and read it from disk.
  5. Parse: convert the workbook into structured items (rows → items).

Prerequisites

  • Windows host (local executable and filesystem paths).
  • DDC Revit toolkit installed: C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe.
  • A local .rvt you can read; the converter will write *_rvt.xlsx next to it.

How to use

  1. Import this JSON into n8n.
  2. Open “Setup - Define file paths” and set:
    • path_to_revit_converter: C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe
    • revit_file: e.g., C:\\Sample_Projects\\your_project.rvt
  3. Run Manual trigger.
  4. On success, the flow will read *_rvt.xlsx and emit parsed items.

Outputs

  • On disk: <YourProject>_rvt.xlsx (created by the converter).
  • In n8n: parsed rows as items, ready for Transform/Load phases.

Notes & tips

  • If your converter writes the Excel to a different folder/file name, update the “Success - Create Excel filename” node to point to the actual path.
  • Ensure write permissions in the project folder and avoid non-ASCII characters in paths when possible.
  • This template is purposefully minimal (Extract-only). Chain it with your own Transform/Load steps.

Categories

Data Extraction Files & Storage EL CAD/BIM

Tags

cad-bim, revit, ifc, dwg, extract, xlsx, etl

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 EL 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

$9.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Other workflows

More from Artem Boiko

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.