@Pranav,
There are a few ways you could do this. The easiest approach is probably to just design your process to do what you've laid out in your steps and then expose that process as a SOAP service. From their you can invoke from a browser or another other applications that can make a web service call. However, this is all that scalable.
A better approach would be to expose a VBO that just accepts the request and puts it in a work queue. From there, you'd have a monitor process, running on a schedule, that would periodically check the work queue for results. When there's work to do, it kicks off the process that would do the work you outlined above. Then that process, the worker process, could issue an HTTP POST back to the initiating system - assuming some sort of identifier was passed along with the initial request (ex. a URL).
Cheers,
------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------
