Questions from you about Robomotion

Production Robot is the software that executes your automation, you install them into your machine or your servers. These Robots can be scheduled to run automations. A Development Robot is only for developing a flow and can not be scheduled to run an automation. Ideally if you have an RPA Developer team, you would prefer Dev Robots for them since it is cheaper. And you deploy their automations to Production Robots. So in short production robots are more powerful, you can schedule, deploy on them, or you can develop your automations on them.

A flow is the automation you develop. 1 Robot can run 1 Flow at a time.

The robot runtime is unlimited, a flow run count is unlimited. 1 Robot can run 1 flow at a time. If it takes 5 minutes to execute and finish, you can run another flow on the robot. If it takes 1 hour to finish a flow, you can run another flow after 1 hour of this execution.

Yes, one way to do it; creating a flow that begins with the “Http In” node. This way when flow starts it immediately starts listening to the REST endpoint. You can post a message there to trigger an action.

Robomotion is a drag-and-drop, visual automation builder tool but you need some basic knowledge of Javascript. We are trying to minimize this need with our recorder tools that are work in progress.

Robot runtime is unlimited. Schedules are used to start a flow running on a robot. This can be every 5 minutes, every 1 hour or every Monday at 9:00 am.

You can run 10 flows every 5 minute but only 1 will manage to start on a robot. All the other flows will be waiting in pending schedules. If the flow finishes, one of the waiting flows will start, and so on.

You get 1 workspace with 10 robots. But you can manage your clients with 1 workspace, maybe renaming your robots per client as a suggestion. Or you can use a few for your clients with time slots.

An audit log is an unchanged log of what anyone did in your workspace as an admin. ABC created a schedule, or deleted a schedule, invited x user, all of these actions are recorded in these logs.

A job log is the result of your automation. It may be finished successfully or with an error. You can log out from these logs.

We have 3 kinds of triggers;

1. File System trigger: fires when a file is created, deleted or modified in a filesystem directory that the robot is watching.

2. Mail trigger: this is actually a mail polling trigger within the intervals you set, trigger just watches for subject and body patterns in an email, if found fires a flow

3. HTTP trigger: this is a little complex, the idea is, this is a web service endpoint e robot listens in the background, when any request comes, robot puts the request in a queue and fires a flow. This flow gets the request from the queue and processes it.

The 4th and most used one is actually time triggers or schedules.

No, a flow is 1 project, it can have as many subflows as you need to.

You can automate any web site repetitive task, social media sites may block you or throw a captcha, proxies would help.

You have to create the flow for this task, but it can be done.

You have 60-days after your purchase for that.

You can contact us via sales@robomotion.io.


Robomotion, like most RPA products, is a low-code tool. So you need some scripting knowledge. In the case of Robomotion, this is Javascript. You need basic knowledge of JS.


We have plans to open an RPA Freelancer marketplace. This will be similar to Upwork, you will be able to post your automation requests with a budget, and someone from the community will bid for them.

You can upgrade from Admin Console -> Licenses.

Depends on your automation. If you use hw keyboard and mouse in your flow, no you can’t. But for web automation you do not need these, a web automation may run in the background with lots of non interrupting tasks, like reading a file from FTP, uploading a file to Google Drive, processing excel files. These all can be done in the background.

We have integrations with Google Cloud Vision API that supports languages other than English. We also have integration with Abby Cloud API, we also have support. These are all online services. You can also use our tesseract package for offline OCR, which also supports languages other than English.

Texau is a no-code platform targeting growth and lead-generation niche, providing ready to use recipes.

Robomotion can also do these, but we have to create these automations for you or you can create them for yourself.

But Robomotion is a low-code automation platform, and it is best for automating custom web or desktop applications that do not provide an API. For example, if you log in to a partner’s portal, navigate through the menus, search some part numbers and get the latest prices into Excel to prepare a proposal for your customer and do these tasks daily, this is a repetitive task that Robomotion can do for you.

RoboTask looks like a Windows Desktop macro recorder.

Robomotion robots are mobile; you can install them into Linux, Mac, and Windows, and from the Admin Console you can command your robots. Robomotion also has a visual flow designer.

For power automate we once prepared a comparison table => https://docs.google.com/spreadsheets/d/1THNpaD9kwzZ47AYik3WuJVxs2N31pyfRDOGuSB33X8w/edit#gid=0

Not very familiar with the tool but I watched their video, it looks like a nice multiplatform macro recorder desktop app for only web automation. You can do these automations with Robomotion and more. We provide a workspace for you. Robomotion provides a visual drag and drop development tool called Flow Designer. You can create not one sequence but 10s or 100s of more branches of sequences in 1 flow. All may run in parallel within 1 robot.


Robomotion is a low-code automation platform. We support JS as our native scripting language. But we provide extensions with custom packages, that you can write in C#, Java, Golang and Python. => https://github.com/robomotionio/robomotion-contrib here are some examples.


You can install 3 robots in different machines, you just press play and select the robot to run your flow remotely. You can create/read Excel files, integrate with Google Sheets, write read data from your filesystem. Your robot also may serve a web service in front of these automations, this way you can turn a web automation into a web service.

You can solve captchas with the Tesseract package from our repository, or if it is an advanced one, you can use captcha solver services.


Here is a ReCaptcha solver example https://explore.robomotion.io/templates/recaptcha-solver using one of these services.


We have created a package for one of the providers also, so you can use it in your flow as one drag and drop node.

Yes, it can do both. Robomotion is a low-code development environment.

You can scrape from one site and upload to another site, generate an Excel file and email it. You can also extract data and generate a daily SQLite DB file.

Robomotion can do much more powerful things, then just pausing for a few seconds. It can wait for a page element to show up with a timeout, so no waste of time waiting more than you need to.

A flow is the automation you create, you can checkout out simple examples here => https://explore.robomotion.io


A robot is the software that runs these flows. You have 24h hours of your robot to fill. 1 flow may take 5 minutes or maybe 30 min to complete or 4 hours. It depends on the automation. Then your robot is free to run other flows.

I repeated the same error in the package, and we have now fixed the problem. Please just use the 0.2.0 version of that package and you will see that the problem has been solved.

If that is a Windows machine and a cloud VPS-like setup and tools can be installed on it, sure it can be done.

We are on Discord! Join us to always be updated with the latest improvements about Robomotion.