The /cloudfiles/store Robot

Our /cloudfiles/store Robot

Transloadit is happy to export to whatever storage solution suits you best.

The /cloudfiles/store Robot exports encoding results to Rackspace Cloudfiles.

The /cloudfiles/store Robot's Parameters

Name Type Default Description
container (required) String The name of the container to which to export the file. Please only use the top level container name. If your container name contains a slash ("/"), then you are setting the wrong name here. Please use the path parameter for "folders" that are within your container.
user (required) String Your Rackspace API user name.
key (required) String Your secret Rackspace Cloudfiles API key. This is not your Rackspace account password. It is the API key.
account_type String "us" The type of your account, which can be "us" or "uk". For details, see the Rackspace documentation.
data_center String "dfw" The data center to use for your account. This is ignored for "uk" account types. Can be "dfw" for Dallas, "ord" for Chicago or "syd" for Sydney.
path String "${}_${file.url_name}" The path at which to store the file. This value can also contain Assembly variables.

Example use cases featuring the /cloudfiles/store Robot

See the robot in action with some live demos and code samples right here on our website:

Store uploaded files in your Rackspace Cloudfiles container

Here you can see a quick example of the Assembly Instructions required to create this encoding pipeline. More information is available in the Live demo

 "steps": {
    "store": {
      "use": ":original",
      "robot": "/cloudfiles/store",
      "user": "YOUR_CLOUDFILES_USER",
      "key": "YOUR_CLOUDFILES_KEY",
      "container": "YOUR_CLOUDFILES_CONTAINER"

Blog posts for Our /cloudfiles/store robot

Over the years we wrote the following posts about Our /cloudfiles/store robot on our blog:

Did you know?

You can easily combine Robots to create powerful workflows, unique to your business.

This is the power of Transloadit.