Hi @Anonymous,
That requirement is a bit tricky because you don't want to end up in a Power Automate flow loop 😁
So, somehow we need to trigger the flow when a new folder is created but not trigger the flow ourselves when we create those 6 folders via our flow.
I would probably say some additional trigger conditions would be the easiest. Below is an example of that setup.
1. Add a When a file is created (properties only)
2. Add the following trigger conditions in the settings of that action. Make sure you add all 6 of your folder names from the array so they are excluded to trigger the flow. In my example I only added 2. The first condition is to make sure the created file is a folder.
@triggerOutputs()?['body/{IsFolder}']
@not(equals(triggerOutputs()?['body/{Name}'], 'NDA'))
@not(equals(triggerOutputs()?['body/{Name}'], 'Terms & Conditions'))
3. Add Initialize variable action. Make it of type Array. You can use the following array as an example.
[
{
"SubFolder": "Terms & Conditions"
},
{
"SubFolder": "NDA"
},
{
"SubFolder": "Questionnaires"
},
{
"SubFolder": "SOW"
},
{
"SubFolder": "Other docs"
},
{
"SubFolder": "Terms & Conditions/Archive"
}
]
4. Add a Parse Json action. Use the SubFolders variable as content and the following Schema:
{
"type": "array",
"items": {
"type": "object",
"properties": {
"SubFolder": {
"type": "string"
}
},
"required": [
"SubFolder"
]
}
}
5. Add a create new folder action. Use the name of the original folder together with the subfolder dynamic content field in the folder path field. This will put the action inside an apply to each loop.
@{triggerOutputs()?['body/{Name}']}/@{items('Apply_to_each')['SubFolder']}
