The flow
Starts it 1Logic 11Service 4
The steps in the order they run, from what starts it.
- 1Start - Click to beginManual triggerStarts it
- 2Setup - Define file pathsSetLogic
- 3Extract - Run Revit converterExecute CommandService
- 4Check - Did extraction succeed?IfLogic
- 5Error - Show what went wrongSetLogic
- 6Success - Create Excel filenameSetLogic
- 7Extract - Read Excel file from diskRead Binary FileService
- 8Extract - Parse Excel to dataSpreadsheet FileService
- 9On the standard 3D ViewIfLogic
- 10Transform - Filter only OST_WallsIfLogic
- 11Non-3D View Elements OutputSetLogic
- 12Transform - Clean wall dataSetLogic
- 13Transform - Group by Type Name & sum VolumeFunctionLogic
- 14Transform - Generate HTML ReportFunctionLogic
- 15Load - Save HTML ReportWrite Binary FileService
- 16Success - Final resultsSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.