Data Extraction and Parsing from Revit Files to Structured Excel - n8n Workflow

BIM Managers and Coordinators needing to automate data reports.
Data Engineers processing construction (AEC) data.
Developers looking for advanced examples of using the n8n node for local command execution.
Users requiring reliable ETL processes for CAD/BIM data within an n8n workflow.

Processing complex BIM (Building Information Modeling) files like Revit (.rvt) often requires external, specialized tools. This advanced n8n workflow template demonstrates a robust and repeatable ETL (Extract, Transform, Load) pipeline for highly specialized data sources. This specific n8n workflow focuses on the 'Extract Phase'—the critical first step in turning proprietary file formats into machine-readable data.

The workflow uses an n8n node to execute a local Revit conversion utility (like RvtExporter.exe), which converts the large, complex Revit file into a standard, structured Excel (.xlsx) file. It then uses core n8n functionality to read and parse this structured data, making it available for subsequent transformation (T) and loading (L) stages in the overall n8n workflow. Using this n8n template ensures that your specialized data processing remains automated and transparent.

This n8n workflow is initiated by a manual n8n trigger and follows a meticulous extraction process:

1. Start and Setup: The workflow begins with the 'Start - Click to begin' manual n8n trigger. Immediately following, the 'Setup - Define file paths' n8n node defines two essential local variables: the path to the Revit converter executable (RvtExporter.exe) and the full path to the input Revit file (.rvt).


2. External Execution: The 'Extract - Run Revit converter' n8n node utilizes the Execute Command functionality to run the external program, passing the Revit file path as an argument. This step generates an intermediate .xlsx file containing the extracted data.


3. Success Check: The 'Check - Did extraction succeed?' If n8n node verifies the output of the command execution. If an error message is detected, the flow branches to an 'Error' handler.


4. Success Branch: If extraction is successful, the 'Success - Create Excel filename' n8n node dynamically generates the expected name of the output Excel file based on the input path.


5. Read and Parse: The 'Extract - Read Excel file from disk' n8n node reads the generated binary .xlsx file. This binary data is then passed to the 'Extract - Parse Excel to data' Spreadsheet File n8n node, which converts the file contents into structured JSON objects, making the BIM data ready for the next stages of the n8n workflow.

To install and utilize this n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON code. In your n8n instance, go to the 'Workflows' section, click 'New', then 'Import from JSON', and paste the code.


2. Install Prerequisites: This n8n template requires a specialized external application (like RvtExporter.exe) capable of converting Revit files to Excel. Ensure this executable is installed and accessible on the machine running your n8n instance.


3. Update File Paths: Open the 'Setup - Define file paths' n8n node.

1. Activate and Run: Save the n8n workflow, activate it, and execute the 'Start - Click to begin' n8n trigger to test the conversion pipeline. Ensure your n8n user has the necessary permissions to execute local commands and access the specified file paths.

Start - Click to begin (Manual Trigger):
Function: Acts as the manual n8n trigger for testing and initiation.
Key Configuration: Standard manual execution.
Setup - Define file paths (Set):
Function: Standardizes the input parameters (file paths) used throughout the n8n workflow.
Key Configuration: Defines pathtorevitconverter and revitfile as local variables.
Extract - Run Revit converter (Execute Command):
Function: Executes the external executable responsible for converting the .rvt file to a structured .xlsx file. This is a critical n8n node for integrating custom local tools.
Key Configuration: Command value is dynamically built using the variables set in the previous n8n node: "{{$json["pathtorevitconverter"]}}" "{{$json["revitfile"]}}".
Check - Did extraction succeed? (If):
Function: Controls the flow based on the success of the external command, checking if the command output contains an error property.
Key Configuration: Condition checks if {{ $node["Extract - Run Revit converter"].json.error }} exists.
Extract - Read Excel file from disk (Read Binary File):
Function: Reads the binary data of the newly created Excel file from the local disk.
Key Configuration: File path is dynamically set using the xlsx_filename variable created previously.
Extract - Parse Excel to data (Spreadsheet File):
Function: Takes the binary Excel file input and parses its contents into an array of structured JSON objects, ready for downstream processing within the n8n workflow.
Key Configuration: Defaults, operating on the binary data provided by the preceding n8n node.