Registry / workflow / robocorp

robocorp

JSON →
library3.1.1pypypi✓ verified 87d ago

Robocorp provides core Python libraries for robotic process automation (RPA), enabling developers to create and manage automated tasks. It includes modules for task orchestration, work item management, and integration with the Robocorp platform. The current version is 3.1.1, with regular updates typically released multiple times per quarter.

pip install robocorp
INSTALL
IMPORT
SIG · ROBOCORP
R
robocorp
workflowpythonv3.1.1
Install
4.4s avg
Import
46ms
Disk
46MB
Pass rate
9/ 10
Env Coverage9 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v3.1.1 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
glibc
py 3.10
✓ —
✓ 5.08s
py 3.11
✓ —
✓ 4.23s
py 3.12
✓ —
✓ 3.63s
py 3.13
✓ —
✓ 3.6s
py 3.9
✕ build_error
✓ 5.68s
46MB installed
● package 46MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

task
from robocorp.tasks import task
from robocorp import task
As of v2.0.0, the task decorator moved to the `robocorp.tasks` module.
inputs
from robocorp.workitems import inputs
from robocorp import workitems
As of v2.0.0, work item management moved to the `robocorp.workitems` module.
outputs
from robocorp.workitems import outputs
Accesses the current output work item.
page
from rpaframework.browser import page
from robocorp.browser import browser
While `robocorp.browser` (v1.x) is still bundled with `robocorp` v3.x, for the latest browser automation features, users should explicitly install `rpaframework-browser` and import from it.

This quickstart demonstrates creating a simple Robocorp task that reads data from an input work item, processes it, and then writes the result to an output work item. It highlights the core 'task' decorator and 'workitems' modules, which are central to Robocorp automations.

import os from robocorp.tasks import task from robocorp.workitems import inputs, outputs @task def minimal_task(): """ A basic Robocorp task that reads an input and writes an output. To run locally, create a 'work-items/input.json' file in the root of your project with content like: `{"message": "Hello Robocorp!"}` Then execute with `python -m robocorp.tasks run -t minimal_task`. """ try: # Access current input work item payload input_payload = inputs.current.payload message = input_payload.get("message", "No message provided.") print(f"Received message: {message}") # Process the message processed_message = f"Processed by Robocorp: {message.upper()}" # Create an output work item and save processed data output_item = outputs.create() output_item.payload["processed_message"] = processed_message output_item.save() print(f"Wrote output: {processed_message}") except Exception as e: # In a real scenario, you'd handle errors more robustly for Control Room visibility print(f"Task failed: {e}") raise # Re-raise to indicate task failure
robocorp --version
Debug
Known issues
breakingThe `robocorp.browser` and `robocorp.windows` modules included directly in the `robocorp` package are frozen at older versions (1.x as of `robocorp` v3.x). For up-to-date and feature-rich browser or Windows automation, you must explicitly install `rpaframework-browser` and `rpaframework-windows` and import from those packages (e.g., `from rpaframework.browser import ...`).
fix
For new projects or updated features, `pip install rpaframework-browser rpaframework-windows` and update imports to `from rpaframework.browser import ...` or `from rpaframework.windows import ...`.
affects: >=3.0.0
breakingMajor refactor in v2.0.0 moved primary task and work item functionalities into dedicated sub-packages. Old imports like `from robocorp import task` or `from robocorp import workitems` no longer work.
fix
Update imports to `from robocorp.tasks import task` for task decorators and `from robocorp.workitems import inputs, outputs` for work item management.
affects: >=2.0.0
gotchaRobocorp tasks operate within a specific environment, heavily relying on 'work items' for input and output data. When running tasks locally or debugging, ensure you provide valid `work-items/input.json` files to simulate the expected inputs, or tasks might fail attempting to access non-existent data.
fix
Create a `work-items` directory in your project root with `input.json` (and optionally `output.json`) files containing sample data. Use `rcc` or `python -m robocorp.tasks run` commands for local execution to ensure the environment is correctly set up.
affects: All versions
gotchaWhile `robocorp` is the core Python library, Robocorp's ecosystem includes other critical tools like `rcc` (Robocorp Command Center) for environment management and `Action Server` for exposing automations as APIs. These are separate installations and tools, and the `robocorp` library itself doesn't directly provide their functionality.
fix
Understand the role of each tool in the Robocorp ecosystem. Install `rcc` separately for environment control, and `robocorp-action-server` if you need to create HTTP APIs for your automations.
affects: All versions
Errors
Common errors & fixes
ModuleNotFoundError: No module named 'robocorp.tasks'
The `robocorp` library, or its specific `tasks` submodule, is not installed in the Python environment being used.
fix
pip install robocorp
rcc: command not found
The Robocorp Command Center (RCC) tool is either not installed or its executable path is not added to the system's PATH environment variable.
fix
Install the Robocorp Command Center (RCC) tool from the official Robocorp website or via the Robocorp Lab / VS Code extension.
FileNotFoundError: Missing input work item 'work-item-in/work-item.json'
When running a robot locally, the required input work item files are not found in the expected `work-item-in` directory within the robot's root.
fix
Create a `work-item-in` directory in your robot's root and populate it with a `work-item.json` file or other necessary input files.
Task 'my_task_name' not found in robot
The specified task name does not match any function decorated with `@task` in the robot's Python files, or the task file is not correctly discoverable.
fix
Ensure the task function is decorated with `@task` from `robocorp.tasks` and that the name used to invoke the task (e.g., with `rc task run`) exactly matches the function name.
Upgrade
Version history
3.1.1latest on PyPI · released Mar 13, 2026
Audit
Dependencies

No dependency data recorded yet.

Agent activity
24 hits · last 30 days
node
20
OpenAI (training)
1
Resources