Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
Power Apps
Score 8.1 out of 10
N/A
PowerApps is a low code / rapid application development product from Microsoft that allows users to quickly build apps.
Microsoft Power Automate is worlds ahead of Zapier in so many ways. The looping, DOM access, and flow controls are much better. I feel that accessing different data within previous connectors used in a flow is much easier in Microsoft Power Automate as well.
We are a full Microsoft Stack user. We use Power Apps for custom applications, Power BI for data analytics, Teams for communication and this software to tie all our solutions together. Microsoft Power Automate (formerly Microsoft Flow) has connectors into most, if not all, of …
Nintex is a more powerful workflow tool, but Microsoft is closing the gap with Power Automate. Microsoft Power Automate can do simple tasks very well, and they both can connect to multiple other systems very easily.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to …
PowerApps and Power Automate go together in the Power platform. They are made to work together to create a vast collection of connectors and out of the box pieces that come together to make a whole application. If you are unable to complete a task from within PowerApps, Power …
PowerApps is the first we have used in Office 365 and Azure Integration. It really helped us to integrate application in Azure and building short apps with low cost.
I'm not sure if you can say D365 CRM is an alternative to PowerApps, because basically all the customization of using D365 CRM, or what used to be called XRM, is now called a model-driven PowerApp. Likewise, SharePoint has become intimately connected to canvas PowerApps. Both …
Microsoft Power Automate is the best tool to extend Microsoft services you already use. Hands down. Prototyping workflows is very easy in Microsoft Power Automate. It's also the best choice for sending custom cards through Teams and email. It's the easiest way to get data from Microsoft Graph.
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
Power Automate has an intuitive interface that is easy for novices to use. It doesn't require programming knowledge, however having that experience will help troubleshoot potential issues if they do arise. There are advanced features that allow the use of "code-like" steps that will help power users get more advanced automations set up quickly.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
I really have had a need to contact Win Automation support, but when I do google how to do a task, Win Automation has an extensive message board with a broad number of topics and questions answered where I could see how other people were able to solve similar problems to the ones I have.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I had to migrate from Robocorp to Power Automate. The automation was using API and sharepoint. So it was better to use Power Automate instead of Robocorp so we did the migration. in some areas the migration was easy but creating flows and making it smaller codes was difficult. Debugging the code was tough so we took lots of time.
Power Automate is a no-code/low-code solution tailored for workflow automation, data integration, and AI integration, making it an excellent choice for Microsoft-centric organizations. OutSystems, on the other hand, is a comprehensive application development platform, offering rapid app development with both low-code and traditional development options. This platform is well-suited for organizations seeking custom application development. Nintex specializes in workflow and process automation with a strong focus on SharePoint and Office 365 integration. It also includes advanced features like document generation and robotic process automation (RPA).The choice among these platforms should align with your organization's specific needs, considering factors like integration requirements and the desired level of technical expertise. In the bottomline, it's up to cost and licensing.
Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows that you can build yourself vs using NetSuite engineers to build it for you.
It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
As lists and libraries change, the platform scales pretty well.
Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.
