Code
Node.js or Python robots whose code comes from a Git repository or a .zip, published by deploy and run on the workspace's devices.
Code
A code project is a robot written in Node.js or Python that runs on Roberty's infrastructure. The code is not edited on the platform: it comes from a synced Git repository (GitHub, Azure DevOps, GitLab or Bitbucket) or from an uploaded .zip file, and the Runner executes it on the Windows devices linked to the project.
Use code projects when an automation is better written as code — API integrations, data handling, routines that already exist in Node.js or Python — and you want Roberty to take care of publishing, scheduling, triggering and recording the runs.
From code to run
Every project follows the same path, the delivery pipeline:
- Code source — the Git repository connected to the project, or the uploaded .zip. See Code source.
- Deployment — on every push to the configured branch (or every .zip upload), Roberty validates the project's structure, installs its dependencies and delivers the code to the environment's devices. The first deployment activates the project. See Deployments.
- Devices — the machines that run the project. With no linked device holding a ready deployment, the project does not run. See Devices.
For the platform to know how to start the robot, the project needs a roberty.json file at its root. See Preparing the project.
Environments: Production and Preview
| Environment | Devices | What it is for |
|---|---|---|
| Production | Many | Real execution: API calls, schedules and manual runs. |
| Preview | One per project | Test environment: manual runs and evaluations, without touching Production. |
In a Git project, each environment gets its code from its own branch. Projects that receive code by .zip only have the Production environment.
Run triggers
A code project can be run in several ways:
| Trigger | How it starts |
|---|---|
| Manual | From the project's Run button, choosing the environment and the device. See Runs. |
| Schedule | A recurrence set per Production device. See Schedules. |
| Webhook | A call to the public API with a workspace API key, with arguments and a response. See API and webhook. |
| Evaluation | Test sets with inputs and an expected output, run on Preview. See Evaluations. |
An RPA robot can also run a code project with the Run Code project action.
Where projects live
Code projects are created and organized in the workspace's Files tab, alongside robots, sub-routines and agents. An open project is laid out in tabs: Overview, Deployments, Runs, Evaluations and Settings.
The Overview shows the project's numbers — runs in the last 24 hours, the success rate of finished runs, average duration and total runs since the project was created — and the delivery pipeline, where each step opens the place it is managed from.
If the project is turned off, runs from the Studio and the API are blocked until it is turned back on in Settings.