We can discuss Microsoft Flow and Azure Logic Apps together because they are both configuration-first integration services. They make it easy to build processes and workflows and integrate with various SaaS and enterprise applications.
- Flow is built on top of Logic Apps
- They have the same workflow designer
- Connectors that work in one can also work in the other
Flow empowers any office worker to perform simple integrations (for example, get SMS for important emails) without going through developers or IT. On the other hand, Logic Apps can enable advanced or mission-critical integrations (for example, B2B processes) where enterprise-level DevOps and security practices are required. It is typical for a business workflow to grow in complexity over time. Accordingly, you can start with a flow at first, then convert it to a logic app as needed.
In one of my other blog posts, I had shown how AgilePoint NX can be integrated with Microsoft Flow
There are minor differences on how integration would work with Logic Apps which is shown in the video referenced below.
Update – 9/22/2017 : On Sept 22nd 2017 i.e a day before Microsoft Ignite 2017 conference, Microsoft announced support for custom “Logic App Connector”.
So though in the video posted below, I showed how you can consume AgilePoint NX Swagger API using HTTP + Swagger activity in Logic Apps, you can now define connector and consume it natively just like I showed in the blog post in Microsoft Flow. However the approach shown in video link below is equally acceptable approach.
So next time someone asks you if an AgilePoint process can be kicked off based on an non native external event, before trying to create one, first look at the list of available triggers on Logic Apps and if a trigger is available over there then the answer would be yes.