Did you ever wonder what is new in Microsoft Flow?
As a large part of Microsoft Flow is its connectors into other applications I though I use the List Connectors action and update a SharePoint list with the connector details. Step one is to create a custom list called Connectors. Initially I’m only creating the Title field but later on I will also collect the connector details for each connector.
The above gives me currently 193 connectors. At a later stage I will turn this into a recurrence flow. But for now I’m using the manual start of the Manual trigger a flow trigger
As I only want to add new connector items in my connectors list if the connector hasn’t been added before I will check in my list if I already have an item with the matching Title using the Get items action.
When the above get items action doesn’t return an item in my Connectors list I will need to create a new item in the list and when an existing item is found we’ll update the details of the connector list item.
The expression used in the below condition should be :
@empty(body('Get_items')?['value'])
I am waiting for the details of actions and triggers to become available so that those details can be stored in the list too.
Now we now what the new connectors are.
Now all I had to do is update the view so that it is sorted by the Connector Created Time and I can see which connectors were added recently.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com
Thanks, this looks like it will be helpful for several of my clients. I would like to take this step further and keep track of when connectors and modified, as well as what the changes included. Do you have any suggestions about how to accomplish this?
Hi Dean,
There is a lot more information about the connectors returned by the List Connectors. I created a flow that copies descriptions, tags (like preview, production). I guess all of this information can be stored in the same connectors list. i could also imagine copying the action and trigger details in a similar way.
in the Apply to Each block, what is the first data operation you show doing?
I am setting that to the title of the connector just for debugging purposes in the run history
After doing my best to follow your steps, i have flow that is completing without errors, but the Connectors list is not getting populated with the new items. When I review the completed flow, I see that it going to the No branch after the Anything Found branch and there is nothing it my new list to update. Any idea what I might be doing wrong?
Hi Dean,
Thank you for letting me know. I’ve updated the post slightly.
Thanks for the update. i got it working now. Another question – how did you add the Properties fields you show in the Update Item screen shot
Adding to the list is just a matter of adding them to the list. I didn’t worry about content types etc.
You will then find that flow doesn’t know about these fields. All you need to do is close the editor and reopen the editor and Flow will then offer all the available fields in the list.