Block 1 - Start - Click to begin
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
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...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Artem Boiko.
Original n8n.io sourceConvert 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.
path_to_revit_converter and revit_file.RvtExporter.exe "<converter>" "<revit_file>" (writes *_rvt.xlsx next to the RVT).<revit_file> → *_rvt.xlsx and read it from disk.C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe..rvt you can read; the converter will write *_rvt.xlsx next to it.path_to_revit_converter: C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exerevit_file: e.g., C:\\Sample_Projects\\your_project.rvt*_rvt.xlsx and emit parsed items.<YourProject>_rvt.xlsx (created by the converter).Data Extraction · Files & Storage · ETL · CAD/BIM
cad-bim, revit, ifc, dwg, extract, xlsx, etl
DataDrivenConstruction.io [email protected]
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
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.
| 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 |
Use the JSON export at /data/workflows/7654/7654.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.