robocorp-workitems
Work items are used in Robocorp Control Room for managing data that go through multiple steps and tasks inside a process. Each step of a process receives input work items from the previous step, and creates output work items for the next step.
Getting started
The library exposes two objects, inputs and outputs, which are the main way to interact with work item queues. The former deals with the reading input work items, and the latter with creating output work items.
A run inside Control Room will always have at least one work item available to it. The simplest Robot which reads the current work item and creates an output can be done in the following manner:
from robocorp import workitems
from robocorp.tasks import task
@task
def handle_item():
item = workitems.inputs.current
print("Received payload:", item.payload)
workitems.outputs.create(payload={"key": "value"})
Iterating over all available input items in the queue is also easy:
from robocorp import workitems
from robocorp.tasks import task
@task
def handle_all_items():
for item in workitems.inputs:
print("Received payload:", item.payload)
workitems.outputs.create(payload={"key": "value"})
Work item structure
A work item's data payload is JSON and allows storing anything that is JSON serializable. By default, the payload is a mapping of key-value pairs.
In addition to the payload section, a work item can also contain files, which are stored within Robocorp Control Room. Adding and using files with work items requires no additional setup from the user.
Guides
- Reserving and releasing input items
- Creating outputs
- Local development
- Email triggering
- Collecting all inputs
- Flow control with exceptions
- Modifying inputs
Further user guides and tutorials can be found in Robocorp Docs.
API Reference
Explore our API for extensive documentation.
Changelog
A list of releases and corresponding changes can be found in the changelog.
2 maintainers
Release files for robocorp-workitems 1.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| robocorp_workitems-1.5.1.tar.gz | 17.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| robocorp_workitems-1.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.5 kB
Release files / robocorp_workitems-1.5.1.tar.gz
| Download URL | robocorp_workitems-1.5.1.tar.gz |
|---|---|
| Size | 17.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
254b833f01b0c5ffcd421e15140212202f25383ef7e48fcfcc2de70c3970558b
|
|
BLAKE2b-256 checksum How to use checksums |
0c066c1a014364ef0c4f4ef3babd528565d77225ced5be7cd9bcc7cdfa894416
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / robocorp_workitems-1.5.1-py3-none-any.whl
| Download URL | robocorp_workitems-1.5.1-py3-none-any.whl |
|---|---|
| Size | 22.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
653958545ae8375e05b61f7608bc13813ed65ea47cce0be1e7cf885e080f1460
|
|
BLAKE2b-256 checksum How to use checksums |
52fc54f05beca67deeef2280151c7ac822104172a9dcdbde91f8198870670296
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency log
