The flow
Starts it 1Logic 3Service 9
The steps in the order they run, from what starts it.
- 1Start export workflowsManual triggerStarts it
- 2Create folders and run n8n cliExecute CommandService
- 3load exported workflowsRead Write FileService
- 4parse workflowExtract From FileService
- 5Remove root nodeSetLogic
- 6Create JSON file with readable nameConvert To FileService
- 7TAG? Auto deploy to devIfLogic
- 8TAG? Auto deploy to PRODIfLogic
- 9Store named workflowRead Write FileService
- 10Create JSON file with readable name (dev)Convert To FileService
- 11Create JSON file with readable name (prod)Convert To FileService
- 12Store named workflow (dev)Read Write FileService
- 13Store named workflow (prod)Read Write FileService
How it's built
- Starts on
- An event in a connected app
- Steps
- 13, 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. 13 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 13 steps before you point it at anything that matters.