Thanks as always Allan for the prompt and kind reply,
What I’m actually trying to do is to avoid handling the queue from openrpa in order to manage it completely in nodered/openflow and have the robot/openrpa only handle the executions. So the following that you recommend is exactly what I want to avoid:
Perhaps you have some reason why it is not advisable to manage it from node red?
That is why I am trying to pop workitem from nodered but I did not find any example that performs the flow in this way (populate a queue from nodered , then call the item from nodered as well and send it to openrpa to work on it).
The example I provided is as simple as possible for scalability: A form with two fields and a submit button. First field where a web is placed, second field where another web is placed. When sending, a workitem is loaded with the two websites to be opened. The queue is now populated with a workitem.
When executing the queue, it will read the only item that is pending and send it to Openrpa to open the two web pages, openrpa only now comes into play to open the web and then notify nodered that the job has been completed successfully, then node network will be able to mark the item as completed.
That flow is the one that I successfully replicated in the diagram sent above except that the item fails to be marked successfully and I can’t find the correct way to send the data from nodered to openrpa. Here it is critical to highlight that the data is not transmitted in the same way when the payload is sent directly from a form to openrpa as if it were sent from a workitem read to openrpa.