Event Driven Process Automation with K2 and Microsoft Flow
Last Updated Friday, August 16, 2019
Businesses are seeing a proliferation of line of business and data systems, IoT devices and services used throughout their organizations. There is a dire need to not just to connect them, but to use them to automatically convert triggers into an action or response.
To stay on top of all the new cloud services and IoT devices, K2’s intuitive process automation platform offers connectors to web services via REST APIs, SOAP web services etc., significantly reducing app building time. K2 generates all the methods and data structures for a development team and enables integration in real-time with no coding. As a result, developers can integrate faster, leverage reusable integrations, and scale application building rapidly.
The next challenge for developers to tackle? Capturing triggers from such modern IoT devices and services and integrating them into business processes. For example, ‘IF’ any new emails are received, a tweet posted, an IoT button pushed or a new file posted on Box or Dropbox or other cloud services, ‘THEN’ do something.
K2 recently announced a new connector for Microsoft Flow, Logic Apps and PowerApps that works seamlessly with the next generation of K2’s APIs. The new connector enables K2’s platform to integrate efficiently with more systems and services than ever before, and expands on an already richly extensible platform from K2. “K2 connector for Microsoft Flow looks really flexible. Triggering K2 workflows from Microsoft Flow opens up integration possibilities and simplifies integration of our processes”- UK based K2 customer.
Automating trigger based workflows is a typical integration scenario entry point such as notifying a reviewer or approver. Next, the document, email, file or data point often becomes an integral piece of multipart workflow patterns including serial, parallel, rework, nested looping, etcetera, with rules and limits set in a workflow process. Organizations also need the ability to handle exceptions, escalations, error handling, task redirection, SLAs and the other kinds of advanced conditions that are well supported by the K2 platform.
The updated K2 Workflow API leverages a modern, REST-based, Swagger-enabled interface that makes it easy for developers and business users to discover and use the API to build process automation applications rapidly and at scale. The new connector to Microsoft Flow enables users of all types to rapidly utilize the deep functionality and power of K2 in tandem with Microsoft Flow in a visual way – eliminating the need to write code. The connector can be easily configured in Microsoft Flow and Logic Apps using the Swagger file in customers’ K2 Appit for SharePoint instances. In the coming weeks, the K2 connector will be published as a pre-built asset and will be available for Microsoft Flow and Logic Apps. Customers can quickly discover and integrate the K2 platform with their Microsoft Flow and Logic Apps.
Check out this short video to see an overview of the new K2 connector for Microsoft Flow using Workflow APIs.
The benefits of the K2 connector to customers:
Extend current system integration and data integration workflows – K2 customers can utilize Microsoft Flow’s large ecosystem of connectors (100+) to enable many cloud events (including IoT and line of business events) to interact with K2, without coding.
Manage professional or personal tasks – The K2 connector for Microsoft Flow gives customers an ability to automate repetitive tasks that augment their use of K2. For example, a customer may be looking for an easy way to review all tasks assigned to them in a daily email at 4 PM. Customers can still review and action all tasks in K2 Workspace or K2 Mobile and create rules to send email reminders within the workflows, but this connector offers them the freedom to define how they want to view pending tasks.
Build mission critical, trigger driven business apps – When customers want to do more with their Flow process, they can initiate a mission critical process right from Flow. For example, when managing contracts, a Microsoft Flow can notify the team of a new contract posted on MS SharePoint, Dropbox or Box. Once the team is notified, Flow can then expand the use of this process within K2 by initiating contract creation, execution and analysis. This maximizes an organization’s operational and financial performance while reducing financial risk. In addition to using Flow to initiate a K2 process, customers can also make K2 processes call Flows from within its process.
K2 and Microsoft Flow users can leverage the capability of each platform to add even more value to their process solutions.
Want to learn more? Join our live webinar “Trigger Based Process Automation: K2 and Microsoft Flow” with K2’s Senior Product Planner, Renier Britz, and Microsoft Flow Senior Product Marketing Manager, Cathy Dew. They will walk through the benefits of using Microsoft Flow and K2 together and answer questions. Learn more about Microsoft Flow here.