Most of us are finding that as stacks move to the cloud, applications have wide-ranging APIs to connect with. This makes automation much faster and easier using an iPaaS like Workato which features and handles both integration and automation elegantly. Still, there are always those legacy systems that completely lack or have incomplete APIs – so what to do about them?
If that legacy application’s roadmap is to retire in the next 36 months, sometimes building custom connectors for an iPaaS or ESB is too effort-intensive for a limited yield in both times that benefit can be realised and ROI. This is frustrating where the legacy applications are part of high frequency business processes ripe for automation.
Lately, we’ve been working with several customers to add right-sized simple, powerful RPA from Tungsten Automation to our Workato iPaaS deployments to give the iPaaS an economical “set of hands” to interface with those legacy applications.
The use of a product like Tungsten RPA enables customers to extract and load data into these legacy applications and via surfacing data back to Workato iPaaS for process orchestration and event-driven automation into API SaaS platforms.
Most loads and process orchestrations are handled in the iPaaS for speed and simplicity, but when we need to call a robot to work with the legacy app, it’s effortless and elegant with Tungsten Automation RPA’s synthetic API functions.
No need for outsized, complex RPA licensing that offers too little or too much functionality (often contrasting with the iPaaS but markedly weaker in execution ability) or weeks and months trying to get Power Automate to behave only to be hit with unexpected bills.
The benefit of using a tool like Tungsten RPA is a simplistic, inexpensive license structure for tactical use over modular structures offered by the big RPA players.
Comments