New sharepoint folder created to take content and name of folder and put into a sharepoint list

(0) Share

Report

Posted on by ER-26091245-0

I'm hoping someone will be able to help me with the below flow. I need to flow to look in a folder in a sharepoint and be trigged if a new folder is created within that folder. If a new folder has been created I need to flow to extract the file name, and the contents of the file (the file will only contain images, so I need the flow to extract the links to the images). This is my flow, with the help of AI, whenever I run the flow I seem to be getting a false result for the condition. Would someone be able to explain why that is, and if there looks to be anything else wrong with the flow. Thank you!

Step 1)

Step 2)

Step 3)

to get the schema, AI told me to use this in generate from sample: {
"d": {
"results": [
{
"Name": "example.jpg",
"ServerRelativeUrl": "/sites/YourSite/Shared Documents/example.jpg",
"TimeCreated": "2024-11-04T12:34:56Z",
"TimeLastModified": "2024-11-04T12:34:56Z"
},
{
"Name": "example2.jpg",
"ServerRelativeUrl": "/sites/YourSite/Shared Documents/example2.jpg",
"TimeCreated": "2024-11-04T12:34:56Z",
"TimeLastModified": "2024-11-04T12:34:56Z"
}
]
}
}

Step 4)

Categories:

AI Builder

I have the same question (0)

All responses (2)

Answers (0)

Sort by

rixmcx59 158 on at

Like (0)

Report
Copy link

Link copied!

hello, try using "When an item is created" as your initial trigger, then your condition will be true when a folder is created.

Was this reply helpful? Yes No
Suggested answer

Mark Nanneman 993 Moderator on at

Like (0)

Report
Copy link

Link copied!

I have an easy fix for the aspect where you only want the flow to run if it's a folder--however I want to mention that if you're trying to list the contents of the folder this might not be the best approach, considering the flow might be triggered shortly after the folder creation and complete it's run before the files have been uploaded that you are trying to list... You could address this with a delay, but you might also want to think of a different way to accomplish what you're trying to do (there are other ways).

An easy fix for at least the part where you only want to run the flow if it's a folder would be to add a trigger condition to your trigger so you dont' even need the condition (and don't waste flow + action runs on unecessary triggers).

Click the dots, select "Settings"

Click Add under "Trigger Conditions"

enter:

@equals(triggerOutputs()?['body/{IsFolder}'], true)

This will basically filter the trigger so that it only fires if the condition is met.

But back to your original post... are you saying the "IsFolder" = true condition isn't working properly? Does it look like it should be showing true, or what is the issue? Can you post a screenshot of that condition from an actual flow run that isn't working?

It would also be helpful to throw in some compose actions to capture the "isFolder" value from the trigger in an easily acccessible way for troubleshooting.

For example:

It works for me when I try recreating your general concept.

Was this reply helpful? Yes No