Call external API from Microsoft Dynamics 365 CRM online

Question

I want to call an address verification API (Green ID) on CRM Accounts and Contacts. There are two API POST methods to call in two triggering points, 1 - Basic_Verification() needs to be called when a flag field (ready to verify) is changed to true 2 - Specific_Addr_Verification() needs to be called when a user manually clicks on a Ribbon button on the form (PowerApps form Command)

This is a SOAP API, and when calling the API POST methods, I have to build the SOAP message body using the Account/Contact record details.

I am not sure what is the ideal way to develop this functionality. The options I am considering are as below,

1. Create a custom API and MS Flow (Power Automate) to call the API. Then trigger the flow using action, power fx row update or by javascript. Please suggest the best approach for each of the two scenarios above.
2. Create an HTTP request in power automate and trigger it on row update
3. Directly call the API using javascript function (webresource) on button click and form field update events
4. Custom plugin triggered by the event, c# code to send web requests

Or else please suggest any other suitable implementation methods for this scenario.

Answer 1

There is no right or wrong solution. All are suitable viable options, based on your requirements/reusability needs - one or other approach is recommended.

I’ll explain what we did recently, we had some enterprise level Mulesoft APIs and we developed custom connectors around that API. So now all CRM dev teams can use that connector in their Flows based on their needs. Even if needed Flow can be invoked from JS web resource..

Basically it’s standard best practice at each level, therefore it can be rationalized later on. Some opinions will come this is as an overkill.

Answer 2

I built a similar functionality multiple times and the following architecture always worked fine for me:

1. Create Action/Custom API with inputs that accept an address and outputs that return the result of validation.
2. Develop the plugin that performs the validation based on provided inputs and tie it to the Action/Custom API you created in the previous step.
3. Create a JavaScript that handles changes of the address field/on-demand call from the button to call new Action/Custom API and consume the result.

One cool thing in that kind of placing of webservice calls into Action is reusability - it would be possible to use the same mechanism wherever you need it - from JS Code, from other plugins/workflows and lastly from external apps/integrations, great example is Power Automate Flow.