Ideas

It is hard to inspect desktop elements one by one, instead the desktop app can have a record button and generate a subflow for the automation.

Currently, at each update, we have to download the latest version of the installer and execute it on each machine where Robomotion is running. It would be great if we could get automatic updates of the Robomotion desktop app. Or at least perform a push from the Admin Console towards all the connected robots.

Can we have the same attributes available for google doc properties that we do for microsoft word? viz: Font size, Space after, font name and also an add header node that would allow you to format fonts as as a header. Font Justification would also be immensely helpful, Left, Center and right justify the text being added. And finally, the create document node to have parent folder id to force the document creation under a specified folder as opposed to service account root. These would allow us to create documents and work with non windows OS and offer the same experience as windows users get.

At the moment, it is not possible to process files located on OneDrive storage. This is pretty annoying since a lot of files are shared between team members on OneDrive Business, so copying a version of the file locally is definitely not an option, and it is therefore impossible to automate processes involving file updates.

The current process to connect to Google sheet is very not user-friendly. Most of the tool I use (Pabbly mostly) Have a simple connection to Google Sheet. Would be better this way.

Can we have an outlook node for the reply functionality that replies to an email? today its not possible and every new email sent breaks the thread, this might be good to have also in the generic email package. Also consider providing a reply all checkbox in the node to reply to the entire distribution list.

It is hard to inspect web elements one by one, instead the extension can have a record button and generate a subflow for the automation.

I would like for any change on my Google Sheets to trigger a flow.

Some projects have multiple flows associated with them and being able to see them all in a single list would be easier on the mind. We can even organize flows into folders based on category, client or project.

Currently when we develop a subflow that can be used in the same flow or in another flow, we have to copy paste the subflow. This makes it hard to fix bugs in common subflows, you have to fix the same error in every subflow or worse you can miss one. Add Subflow Load / Save support and creating a library of subflows within a workspace.

When you need to manage 10s or 100s of web scraping Chrome sessions with your robot, you most probably want to use the "Headless Chrome" option in your flow. If you are using a Linux machine without a Desktop, this is the only option. But "Headless Chrome" is easily detected by anti-bot measures on some sites, blocking immediately or constantly throwing out reCaptcha's. Puppeteer has a plugin to counter-measure this named stealth plugin. Add this feature to Open Browser node.

Websites can create unique fingerprints to track user activity without even using Cookies. This technique is also used as an anti-bot measure by some sites, blocking usage and throwing out recaptchas. By changing the attributes sent by a browser it is possible to change the identity of a browser. https://coveryourtracks.eff.org/ https://blog.torproject.org/browser-fingerprinting-introduction-and-challenges-ahead/ https://datadome.co/bot-management-protection/detecting-headless-chrome-puppeteer-extra-plugin-stealth/ https://intoli.com/blog/not-possible-to-block-chrome-headless/chrome-headless-test.html https://github.com/berstend/puppeteer-extra/tree/master/packages/puppeteer-extra-plugin-stealth https://bot.sannysoft.com/ Add fingerprint spoofing support.

Notify us when a robot disconnects due to technical error.

Currently, Python, .NET Core, Java, and Golang are supported. Javascript has huge library support and would be great to write custom packages with Javascript.

Hey, I would find it great if there was a little documentation about the individual nodes. Just a short description of what the node does and when it is used (maybe with info if it requires a certain input or gives a certain output). Preferably directly within the flow designer, with the help of a small "i" symbol or something, so that you don't have to switch to the documentation while working on a flow to find the corresponding place. Currently I have the problem that I - as a new user - am often not quite sure which node is suitable for the respective purpose, when I am sitting on a particular flow.