The flow
Starts it 1Logic 11Service 6
The steps in the order they run, from what starts it.
- 1Start - Click to beginManual triggerStarts it
- 2Setup - Define file pathsSetLogic
- 3Create - Excel filenameSetLogic
- 4Check - Does Excel file exist?Read Binary FileService
- 5If - File exists?IfLogic
- 6Info - Skip conversionSetLogic
- 7Extract - Run converterExecute CommandService
- 8Merge - Continue workflowMergeLogic
- 9Check - Did extraction succeed?IfLogic
- 10Read Project Excel FileRead Binary FileService
- 11Set Validation Rules PathSetLogic
- 12Error - Show what went wrongSetLogic
- 13Set xlsx_filename after successSetLogic
- 14Merge Excel FilesMergeLogic
- 15Read Validation Rules FileRead Binary FileService
- 16Validate - EnhancedCodeLogic
- 17Save Validation Report1Write Binary FileService
- 18Open Excel Report1Execute CommandService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 2 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. 18 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.
Nothing 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 18 steps before you point it at anything that matters.