Last week in a meeting client explained requirement:
“.. we receive emails in a mail box, and we manually create contacts in CRM using sender name and address for further processing, we want to automate this.. .”
This task was going to extend existing system functionality but there was no existing code to reuse or modify and of course expectation was to deliver this soon. So it was a perfect case to use Microsoft Business Application Platform. In this post I will explain how easy it was to provide solution using Flow.
Flow is part of Business Application Platform and it is latest service from Microsoft to create automated workflow. It is intended for business and power users so most of the time tasks can be performed without writing a single line of code. Some of its cool features are:
To get started first step is to sign up at flow.microsoft.com. Currently there is a basic “Flow Free” plan which is free, for more details about pricing see this.
There are three basic components in Flow which are connector, trigger and action.
Connector is used to connect to source and target system. A few examples of connectors are Dynamics 365, OneDrive, Gmail, Twitter, Excel, Azure Storage, Oracle, DB2, RSS, Eventbrite or Youtube. At the time almost 227 connectors are available and hopefully this number will increase.
A trigger is an event that occurs inside the connector. For example with SharePoint a few triggers are:
Similarly a trigger with Gmail is when a new email arrives. A connector can have multiple triggers and in a flow usually we chose a trigger which start execution of flow.
After selecting trigger normally next step will be to chose target system or service (again using connector). Similar to triggers with source connector, a target connector may have multiple associated actions to chose from. For example Office 365 Outlook has:
By choosing an action we tell what should happen to target system or server. Good thing is we can chose multiple actions which will be performed one by one. For example we can create a flow which on receiving an email will send a sms, create a file in Sharepoint and also create record in Dynamics 365.
Note:
This demo was created using Gmail, but for Outlook, “Outlook.com” and “Office 365 Outlook” two connectors are available. One catch though is at the time they do not offer senders name as dynamic content. A solution can be to redirect Outlook emails to a Gmail box and configure Gmail to create a contact in Dynamics 365.