Stop unnecessary SharePoint cloud flow runs with trigger conditions
Diesen Beitrag auf Deutsch lesen
Use a Power Automate trigger condition to run a SharePoint folder-copy flow only when a new document set has the Binder content type.
TL;DR
A Power Automate cloud flow uses the SharePoint When a file is created, properties only trigger and a Copy folder action to populate new Binder document sets. Adding a trigger condition for the Binder content type prevents the flow from running for every file added to the library, reducing unnecessary runs and potential billing costs.
Original by Charles, on console.log('Charles');. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Add a trigger condition that checks for the Binder content type before copying the template folder structure, so ordinary file uploads do not start the flow.
- Leadership/Business: Watch flow run volume when a document-set template contains many folders, because unrestricted file triggers can create avoidable billing costs.
Frequently asked questions
How do I limit a Power Automate SharePoint folder-copy flow to Binder document sets?
Add a trigger condition that checks whether the newly created item's content type name is Binder. This prevents ordinary library files from starting the folder-copy flow.
Why does the SharePoint When a file is created trigger cause unnecessary cloud flow runs?
It runs whenever a file is added to the library. A Binder template with more than 50 child folders can therefore generate many unwanted runs.
What does the Copy folder action do in the Binder document-set flow?
It copies the nested folder structure from a separate template library into the newly created Binder. The default document-set content is left empty.