Robotic Process *Analysis*, not automation
The biggest value of RPA tooling is not automation, but Analysis.
While RPA tools are great for screen scrapping, the advent of Single-Page-Application frameworks {Angular, React, Vue, Elm, etc} has rendered a generation of automations redundant because [1] pages are more complex [2] web-services are better suited to traditional integration (even if the integration is node.js mashup)
*Attempting* RPA, is a good way to perform process analysis, but the outcome is just as likely to provide information for an integration project as it is for a robot - and in a small number of low-volume cases it's actually cheaper to get people to do it.
The exception is where the integration touch-points are well understood by the vendor, or they have hooks in the API (usually because they wrote it). This is why Microsoft is likely to be the biggest winner:
[1] Outlook/Exchange/Office365 are the largest automation surface (even if few are using Dynamics, or hosting in Azure), and Active-Directory is the trust mediator
[2] RPA tooling can be discounted for platform lock-in