Skip to content

Orchestrating your automation



Orchestration automation is possible to manage the execution of tasks in an automated way, being able to isolate tasks so that they can be executed sequentially.

BotCity Maestro is an automation platform used to support the development process of bots and other types of automation, deployment and orchestration of processes in runtime.

Life Cycle

The automation process contains a life cycle divided into a few steps:

  • Process Preparation: the developer must know the processing flow.
  • Creating the project: the developer creates the automation project, which can be in Python, Java, Javascript or Typescript.
  • Developing Robot: the robot will be developed in this step.
  • Deploy and Relase on Maestro: after the build is done the developer will send the robot to the platform and choose which version will be used in production.
  • Creating runner: the developer will create the runner.
  • Configuring BotRunner: the developer sets the machineId in the SDK configuration.
  • Creating automation: the developer will create the automation, selecting the Runner that was created and the robot that was deployed.
  • Starting the BotRunner: the developer will start the BotRunner from the terminal.
  • Creating task: the developer or the user who will be responsible for running the robot will create a task for the BotRunner to execute.
  • Task execution: the BotRunner will perform the task.

Creating a project

To build a bot we need to create a project in Java, Javascript or Python structure that will be used to develop the bot.

To create a project follow the tutorials below:


In addition to template projects, you can also orchestrate your own custom projects.

See more details about orchestrate custom projects.


For this tutorial we will be using a Python Web Bot project.

Building your project

To send the bot to Maestro you need to build the project. If you are in Windows run the build.bat file in the root directory of the project, otherwise run the file under Linux or macOS.



If you get a permission error, make sure that your script has execution permission.

You can set the permission with the following command:

chmod +x

Easy Deploy

After building the project, the next step is to deploy the automation to BotCity Maestro.

The easiest way to do your first deployment is through Maestro's Easy Deploy feature.

The Easy Deploy process is basically divided into three steps:

  1. Creating/updating an automation
  2. Deploying a bot
  3. Choosing where to run

Easy Deploy options

To create an automation from scratch, select the option: Create new automation

First Step - Creating an automation

The first step is to fill in some information about the automation process being created.



See more details about Automations management in this section.

Second Step - Deploying a bot

The second step is to fill in the information regarding your bot.

In this step, you will upload the file related to the robot and define the version, the identifier, and the technology being used.

EasyDeploy Step 2

Java project

For Java projects, upload the generated .jar file in the dist/ folder, if it generates two .jar files upload the file with jar-with-dependencies in the filename.

Python project

For Python projects, upload the generated .zip or .tar.gz file in the dist/ folder.

Javascript project

For Javascript projects, upload a .zip file containing the project files such as the bot.js, resources folder and package.json.

Warning for legacy projects

For Python automations, if you are using a legacy project template, the bot identifier must match the id defined when creating the project.

If the auto-generated name is not the same as the ID of the created project, change it so that the identifiers match.

Basically, the bot identifier appears in the name of the generated .tar.gz file being used.

Final Step - Choosing where to run

The third and final step is to define which Runner will be associated with this automation.

EasyDeploy Step 3


To associate a Runner with automation, it must be properly created and configured on the platform.

See more details on how to create and configure a Runner in the Runners section.


In the file located in conf/conf.bcf of the BotCity Studio SDK, ensure that the Runner ID that will be used corresponds to the Runner linked to the automation.

machineId=runner-01  # <- your runner id here

See more details about the BotCity Studio SDK configuration.

Success 🚀

Congratulations 🏆

In a few seconds, you managed to configure your automation process, associate it with your bot and define where it will be executed.

You now have the option to create a new task or schedule for this automation.

By doing so, a new task will be queued and as soon as the Runner associated with the automation is active the execution will start automatically.

EasyDeploy NewTask

Over the next sections, we will cover in more detail how to create and execute tasks.

Automation Management via BotCity Maestro

The Easy Deploy process is very useful for the first deployment of our automation.

However, at certain times we may need to deploy new versions or update existing versions of our bot associated with our automation.

Through Easy Deploy, we can also update automations that already exist on the platform.

Easy Deploy - Existing Automation

After selecting an existing automation, you can edit the robot and the Runners linked to this process.

Updating your bot

On the screen containing the robot's information, you can update the current version being used or upload a new version.

Just upload the robot file and enter the corresponding version.

If you keep the same version already being used, this new file will overwrite the previously used file.

Easy Deploy - Update Bot


If you leave the Release this version option checked, this will be the version used in the next executions of the automation.

Updating Runners

At this stage, you will be able to edit the Runners that are linked to the automation process.

Easy Deploy - Update Runner

Managing tasks

Tasks are instances of an Automation that are created by the user via the Maestro User Interface, BotCity CLI, Maestro SDK or the Maestro API.

Task creation page

You can create a task via the task creation page in Maestro.

Just click on the New Task button referring to the automation process you want to execute.

New Task


The Automation created in the Easy Deploy process will be displayed on this page.


See more details about the New Task page in this section.

Executing tasks

After creating a task, it will be sent to the queue and at that moment it will be ready to be executed.

The last necessary step is to activate Runner. Just run the BotRunner or BotRunner-gui script from the BotCity Studio SDK.

Finishing a task

Once tasks are created, they are queued on the BotMaestro and collected for execution by the BotRunner.

There are two ways to finish a task: via code (together with the bot code) or via CLI.

It is the bot developer responsibility to inform the BotMaestro via the SDK of the proper final status of a task.

Click here to learn how to finish a task using the Maestro SDK.


Finish a task is just one of the possible integrations we can do with BotCity Maestro.

See more details about BotCity Maestro integrations in this section.


Most of the above functionalities can also be done through BotCity Command Line Interface.

See more details about the command lines that can be used.


Q: Runner does not run the robot

  1. Make sure you choose the runner correctly in the automation.
  2. Check if the SDK configuration is with the correct machineId.
  3. Make sure you start the runner.
    • If you have the runner with GUI, click the "START" button to run the tasks in the queue.
  4. Open the log.txt file in the root directory of the SDK and check if there were any errors.
  5. Make sure the runner is running in the terminal.
  6. Check that the runner has internet access.