---
id: robocorp-storage
version: "1.1.0"
license: Apache-2.0
license_treatment: permissive
maintenance: active
---

# robocorp-storage — Robocorp Asset Storage library

License: permissive · Maintenance: active · Downloads: 560.4K/mo

## What it is and what it does

robocorp-storage is a client library for interacting with Robocorp Control Room's Asset Storage service. It abstracts the HTTP communication needed to store, retrieve, and delete assets—text, files, and other types—in a centralized cloud repository managed by Robocorp. The library is designed for use within Robocorp automation workflows, where you need to persist data across robot runs or share state between multiple automation tasks.

The package wraps requests and tenacity to handle HTTP calls and retry logic, exposing a simple Python API (set_text, get_text, delete_asset) that maps directly to Control Room storage operations. It supports modern Python versions (3.10 through 3.14) and is actively maintained by Robocorp, with no known security vulnerabilities.

Use it for:

- Store and retrieve configuration or state data between successive robot runs in Robocorp Control Room.
- Share extracted data or results across multiple automation tasks running in parallel or sequentially.
- Persist temporary or long-lived assets (credentials, reports, logs) without managing external databases.
- Build multi-step automation workflows where downstream tasks need access to upstream outputs.
- Centralize asset management for teams running multiple robots in a shared Control Room environment.

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

Provides read and write access to Asset Storage in Robocorp Control Room, allowing you to store and retrieve text, files, and other asset types from a centralized storage service.

Yes, if you are building automation workflows in Robocorp Control Room and need a simple, low-friction way to persist and share data across robot runs. The library is actively maintained, has no security vulnerabilities, and depends only on two stable packages. Not relevant outside the Robocorp ecosystem.

## Install

pip install robocorp-storage
uv add robocorp-storage
poetry add robocorp-storage

## Installing robocorp-storage

Before you install: Low friction install with only two lightweight runtime dependencies (requests and tenacity). Actively maintained with recent commits and no known vulnerabilities.

License in practice: Licensed under Apache-2.0 (permissive), which allows commercial use, modification, and distribution with minimal restrictions—suitable for most use cases.

Quickstart:

pip install robocorp-storage

from robocorp import storage

storage.set_text("key", "value")
print(storage.get_text("key"))
storage.delete_asset("key")

Requires Python 3.10 or later; requires valid Robocorp Control Room credentials/environment to connect to Asset Storage.

Verify before relying:

- Whether Asset Storage requires explicit authentication setup beyond environment variables in the Control Room context.
- Performance characteristics and rate limits for large asset operations.
- Supported asset types beyond text (e.g., binary files, structured data formats).

## Package facts

- License: Apache-2.0 (permissive)
- Python support: supports_current
- Install friction: low
- Maintenance: active
- Downloads: 560.4K/month (top 15,000 on PyPI)
- Known vulnerabilities: none known

## Tags

robocorp asset storage client, control room storage api, store retrieve assets robocorp, robocorp cloud storage library, asset management robocorp, robocorp storage read write, control room asset access, robocorp-ecosystem, cloud-storage, automation-state

[View on SkillFed](https://skillfed.io/packages/robocorp-storage) · [View on PyPI](https://pypi.org/project/robocorp-storage/)