cancel
Showing results for 
Search instead for 
Did you mean: 
siddharth_v

SharePoint Based Triggers In Microsoft Flow - Part Two

In the previous article, we got an introduction to available triggers  based on SharePoint. We have also learned in detail about 5 trigger points. This article will focus on the next 5 trigger points. 

Trigger - When a file is deleted

 
Description from MS -  Triggers when a file is deleted in a library. You can optionally specify a folder to watch as well. When a folder is deleted, the trigger will fire only once for the deleted folder.
 
This will trigger workflow when an item is deleted from the library, we can also specify a folder if we want to keep a watch on the SharePoint document library folder and only when to trigger when a file is deleted under a specific folder. 
 
1.png
 
  • Site Address - It will list down all the sites collection in our tenant, we can choose anyone.
  • Library Name - It will list down libraries based on site selected above.
  • Folder - Select any folder within the library selected above or keep it blank to trigger workflow when any file is deleted at any level.
Trigger - When an item is created
Desc from MS - Triggers when an item is created.
Do we need any explanation here? MS Flow will trigger when an item is created in the list. It will return all list item properties which can be used in the Flow.
 
2.png
  • Site Address - It will list down all the sites collection in our tenant, we can choose anyone.
  • List Name - It will list down lists based on site selected above.
  • Limit columns by View - This field is to select view so that we can limit the number of columns which are returned.
Trigger - When an item is created or modified 
Desc from MS - Triggers when an item is created, and also each time it is modified.
 
Similar to the above workflow but also triggers when an item is modified. MS Flow will trigger when the item is created or modified in the list. It will return all list item properties which can be used in the Flow.
 
3.png
 
  • Site Address - It will list down all the sites collection in our tenant, we can choose anyone.
  • List Name - It will list down lists based on site selected above.
  • Limit columns by the view - This field is to select view so that we can limit the number of columns which are returned.
Trigger - When an item is deleted 
Desc from MS - Triggers when an item is deleted in a list.
 
This trigger point can be used when we wanted to perform some operation when an item is deleted from the list. Please note that this triggers once an item is deleted so only a few references properties would be available to use in flow (screenshot added below).
 
4.png
 
  • Site Address - It will list down all the site collections in our tenant, we can choose anyone.
  • List Name - It will list down the lists based on site selected above.
  • Properties are available to use in Flow when an item is deleted.

5.png

 

Trigger - When a file is created or modified in a folder 
Desc from MS - Triggers when a file is created, and also each time it is modified in a SharePoint folder.
 
This is similar to when a file is created - This trigger point will return file and it does not return file properties (library columns). We have to either select the folder or provide a relative path of folder like below '/MyDocs/MyFolder'. Please note that we can also select just document library in Folder option. This way it will be similar to the above trigger(when the file is created(properties only)
 
6.png
 
  • Site Address - It will list down all the sites collection in our tenant, we can choose anyone.
  • Folder Id - Here you can select any folder inside any document library or you can select document library.
  • Infer Content Type - If set to yes, the content type will be retrieved by flow from the document.

It will return the below fields to use in Flow.

 

7.png

 

That's it for now, as of now we have very limited options but they are very useful. One of the trigger points which I feel we should have is conditional triggering when one or more particular columns are updated. We can handle this in ms flow using conditional decision point as of now but this will still add flow in run history).
 
Thanks for reading, Let me know in the comments if you feel any other trigger point on SharePoint should be available.
 
P.S - This article was originally posted on this link.
About the Author
  • Experienced Consultant with a demonstrated history of working in the information technology and services industry. Skilled in Office 365, Azure, SharePoint Online, PowerShell, Nintex, K2, SharePoint Designer workflow automation, PowerApps, Microsoft Flow, PowerShell, Active Directory, Operating Systems, Networking, and JavaScript. Strong consulting professional with a Bachelor of Engineering (B.E.) focused in Information Technology from Mumbai University.
  • I am a Microsoft Business Applications MVP and a Senior Manager at EY. I am a technology enthusiast and problem solver. I work/speak/blog/Vlog on Microsoft technology, including Office 365, Power Apps, Power Automate, SharePoint, and Teams Etc. I am helping global clients on Power Platform adoption and empowering them with Power Platform possibilities, capabilities, and easiness. I am a leader of the Houston Power Platform User Group and Power Automate community superuser. I love traveling , exploring new places, and meeting people from different cultures.
  • Read more about me and my achievements at: https://ganeshsanapblogs.wordpress.com/about MCT | SharePoint, Microsoft 365 and Power Platform Consultant | Contributor on SharePoint StackExchange, MSFT Techcommunity
  • Encodian Owner / Founder - Ex Microsoft Consulting Services - Architect / Developer - 20 years in SharePoint - PowerPlatform Fan
  • Founder of SKILLFUL SARDINE, a company focused on productivity and the Power Platform. You can find me on LinkedIn: https://linkedin.com/in/manueltgomes and twitter http://twitter.com/manueltgomes. I also write at https://www.manueltgomes.com, so if you want some Power Automate, SharePoint or Power Apps content I'm your guy 🙂
  • I am the Owner/Principal Architect at Don't Pa..Panic Consulting. I've been working in the information technology industry for over 30 years, and have played key roles in several enterprise SharePoint architectural design review, Intranet deployment, application development, and migration projects. I've been a Microsoft Most Valuable Professional (MVP) 15 consecutive years and am also a Microsoft Certified SharePoint Masters (MCSM) since 2013.
  • Big fan of Power Platform technologies and implemented many solutions.
  • Passionate #Programmer #SharePoint #SPFx #M365 #Power Platform| Microsoft MVP | SharePoint StackOverflow, Github, PnP contributor
  • Web site – https://kamdaryash.wordpress.com Youtube channel - https://www.youtube.com/channel/UCM149rFkLNgerSvgDVeYTZQ/