Well if we want to schedule a robot from orchestrator first it won’t require a api
When orchestrator meets the set time as scheduled it will trigger the connected robot as a agent in your server which means you can just connect the robot to orchestrator so that it will get triggered on set timings
As I’ve explained in my first post: the robot must run “based on some events” generated by that software, so we’re not talking about scheduling here.
If there is a api then we can use webhook to trigger bots
But as there is no api available then the bot schedule has to be designed in a way to run for every 5 or 15 minutes of time and monitor the event change with set of validation activities like element exists or on element appear and if true it will perform the process else it will terminate and wait for next schedule to check the change
It may be a solution, thanks.
But it’s not for my case where instant reaction to the event is critical. It seems that for my case is no solution out there without API.