Once the flow list gets long, it can be hard to find things quickly. Folders help, but it still gets messy. How do you keep yours organized — naming conventions, folders, or something else?
Hello Davijen,
I organize my flows by room and in there by device.
000 house
100 living room
200 bathroom
201 bathroom light
202 bathroom sensor
…
900 software
901 birthday greetings
…
That keeps it easy to find a flow very quick.
The same orgainzation I use for the devices.
I use a folder structure per room subdivided into subfolders per topic (like lighting, curtains) and devices (like Sonos, TV and heat recovery unit). The room folders are sorted in order of importance/most used.
In addition I have a general folder for overarching topics, like power consumption, presence/sleep status and exports of logging & insights.
Finally, I have a dedicated folder for dashboard related flows, with subfolders per dashboard widget app with subfolders per dashboard topic.
Just in folder structure and sub folders.
Test
Living room
Kitchen
Sensors
Machines
Outdoor /sub folder Garage
And so on
Pretty much the same.
I have each room as a main folder. Within them i split down to flow type or device type. Eg lights/blinds/heating.
Like many here i have a folder of test and disabled flows, usually the ones I ask chat gpt to make and need to check
some I know have just one massive list, freaks me out ![]()
I know it’s October and spooky season
but what kind of fresh hell horror story is this… no folder structure ![]()
run ![]()
run for your life ![]()
Whenever I am re-hashing an Advanced Flow, if the original actually works, I just have a mad scientist idea to improve it… I always duplicate the flow and move the copy to the Test folder first, before I start implementing my new hairbrain idea… so at least my home keeps working while I do some crazy on a flow ![]()
This is as well as using the excellent Flow Version History app, and the Backup Centre app to do daily backups to my NAS… and the Homey native nightly cloud backup… I think I have myself covered, no matter how much I FUBAR something ![]()
![]()
![]()
I think, every sysrem is ok as long it fits the users systematic and make it easy to find the flow you want to work on.



