Can anyone share an example of a workflow that dynamically creates and maintains a folder structure in OneDrive?
I’m trying to work on a very straightforward structure:
Invoices/
├── 2024-03/ # Current month folder (format: yyyy-MM)
│ ├── invoices/ # For confirmed invoices
│ │ ├── invoice1.pdf
│ │ └── invoice2.pdf
│ └── other/ # For other documents
│ ├── document1.pdf
│ └── document2.md
│
├── 2024-02/ # Previous month
│ ├── invoices/
│ │ └── invoice3.pdf
│ └── other/
│ └── document3.pdf
│
└── 2024-01/ # Older months follow the same pattern
├── invoices/
└── other/
However, since it’s dynamic, I cannot easily hardcode folder IDs. I cannot even get them from nodes directly because the folder may not be created for every run.
My primary complaint is that OneDrive folder search is VERY limited to the most basic search by folder name, which responds with many results that I cannot filter in the node.
For every such search, I have to create a Filter or Code node so that the result is somehow possible to consume, but it clutters the output…
If I had the possibility to use advanced search, by folder name, path, or even limit by case sensitivity, it would make the experience MUCH better and make workflows much less complicated.