Skip to main content

ETL: Extract and Parse Revit Model Data to Structured Excel

Workflow preview

Workflow preview
100%
ETL: Extract and Parse Revit Model Data to Structured Excel preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Convert a Revit model to Excel and parse it into structured items ready for downstream ETL. This minimal template runs a local , checks success, derives the expected filename, reads it from disk, a...

Best for

  • Engineering automation workflows
  • Multimodal AI automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.executecommand, n8n-nodes-base.if, n8n-nodes-base.readbinaryfile, n8n-nodes-base.spreadsheetfile, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Artem Boiko.

Original n8n.io source

1.1 Workflow description

Title
ETL: Extract and Parse Revit Model Data to Structured Excel
Workflow name
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 ETL. 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 RVT).
  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 · ETL · CAD/BIM

Tags

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

Author

DataDrivenConstruction.io [email protected]

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

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Start - Click to begin

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Setup - Define file paths

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Extract - Run Revit converter

Type / Role
n8n-nodes-base.executeCommand - executeCommand
Config choices
Version 1

Block 4 - Check - Did extraction succeed?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 5 - Success - Create Excel filename

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - Error - Show what went wrong

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 7 - Extract - Read Excel file from disk

Type / Role
n8n-nodes-base.readBinaryFile - readBinaryFile
Config choices
Version 1

Block 8 - Extract - Parse Excel to data

Type / Role
n8n-nodes-base.spreadsheetFile - spreadsheetFile
Config choices
Version 1

Block 9 - Extract Phase Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Extract Phase Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - On the standard 3D View

Type / Role
n8n-nodes-base.if - if
Config choices
Version 1

3. Summary Table

Workflow ETL: Extract and Parse Revit Model Data to Structured Excel
Complexity intermediate
Nodes 14
Categories Engineering, Multimodal AI
Author Artem Boiko
Published 20 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7654/7654.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does ETL: Extract and Parse Revit Model Data to Structured Excel do?

Convert a Revit model to Excel and parse it into structured items ready for downstream ETL. This minimal template runs a local , checks success, derives the expected filename, reads it from disk, a...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, Multimodal AI use case.