Connectors

With the Office 365 connectors being retired, now is the time to move your Microsoft Teams automation to Power Automate. Whether you’re replacing old connectors or building from scratch, this post walks you through creating dynamic, real-time workflows using webhooks. In this blog post, we’ll explore a hands-on tutorial for creating dynamic, real-time workflows in Microsoft Teams, using webhooks and Power Automate. If you’re a Teams user or an IT pro looking to streamline tasks and improve efficiency, this guide is for you. Plus, I’ll show you how to overcome common challenges, like data loss prevention (DLP) policies, and secure your flows with app registrations. ...

Ever tried to post an email attachment directly to a Teams channel using Power Automate, only to find the built-in actions don’t support it? If you receive emails with attachments or generate regular documents, you might want to post them direct to Teams. In this post, I’ll show you how a custom connector makes this possible. I have covered how to build the custom connector in my recent post How To? Build It! Custom Connector. In this post, I will use this connector and share with you my flow. ...

Have you ever fancied your own trigger or action that you can call from Power Automate? This very same connector can be used in PowerApps too or you can build one specific for your Logic App. I am going to show you how I built a custom connector for the Graph API. The API call in question will allow me to post an attachment to Teams chat. This is currently not supported by the native Teams actions in Power Automate. I also have an article on how the flow is built here. ...

Off the back of my Power Platform Quiz concept where I first used the HTTP API, I have built a solution that in real-time will dynamically serve up files hosted on SharePoint, also using the HTTP API in Power Automate! I first learned about this possibility whilst in discussion with Paul at TachyTelic. This is a working proof of concept and I would love to get your feedback. Imagine that you create documents that need to be served up to the public via your website. You might have version control on these and you might want approval. Quite often the file would be saved to a traditional server or onto a SharePoint document library and then comes the time of publishing. You get in contact with your web team, you send them a copy of the document and they publish the file to the website for you. What happens next? You spot a typo and you need to edit the file and have the Web Team republish that file via the corporate content management system. How much time would you spend on this process each time? ...