Summary:
This article describes one business use case integration where “Opportunity” from Microsoft gets converted into the “Company” in Marketo.
Prerequisites:
- User needs to have working Microsoft & Marketo account.
- Working webMethods.io tenant.
Contents:
- This simple use-case describes the step-by-step process of integration between Microsoft & Marketo, where every Opportunity in Microsoft is getting converted into the company in Marketo. This example will also show the mapping steps in the new webMethods.io flow service.
Note:
Any coding or configuration examples provided in this document are only examples and are not intended for use in a production system without verification. The example is only done here to better explain and visualization of the possibilities.
Steps:
1. Login to the webMethods.io & create the new project then choose the flow service then click on the ‘+‘ icon to create the new flow service.
2. Give some name to the flow service, then add the Microsoft Dynamics 365 CRM connector.
3. Now, the user can choose the predefined action “queryOpportunity“ from the drop-down menu or he can make the custom operation as well.
4. Once the action is selected, the user needs to set up the connection. As mentioned in the below screenshot. Users can use “default“ as well as “Manual“ from the options. For this example let choose the default one.
5. Once the account is configured, we will add the ‘try‘ block & we will insert the ‘if‘ condition inside the try block. Inside the if condition we will validate the Output result of the “query Opportunity“ response. We are checking the null scenario.
6. Here, ‘if block‘ has two cases, YES or NO. The flow of execution will proceed based on the if block condition evaluation.
7. Inside the YES path we will add the ‘Marketo‘ connector. Configure the Marketo account details as we configured for the Microsoft.
8. To add the custom operation, the user needs to set up the connection, as mentioned above, the user has the option to choose from the Default & Custom option. For this example, we use the Default option, As mentioned in the below screenshot.
9. Fill the credentials details & click on the Allow button. Now the account is set up for the use & the user can perform operations on this connector.
10. Now, create the custom operation “create Company“ & select all the necessary fields based on the business use case & for fields mapping click on the pipeline icon, as mentioned in the below image.
11. Now map the “queryOpportunitiesOutput“ values to the “createCompany“ input values. As mentioned in the below images. (Use case & filed mapping may differ in the realtime scenario).
12. Now, in the case of “queryOpportunityOutput“ is null. The flow of execution will go to the Else block with the message:- “Opportunity is empty“. But in the case of Positive response, the flow of execution will signal the SUCCESS response. The below images show the entire structure of the Flow service.
13. This Flow service execution shows a simple demo, that handles the error scenario as well. Catch block has the “GetLastError“ service, that informs user for any errors occurred during the flow service execution.
14. Once the Flow service executed successfully, the result will be visible in the result screen.
