The /azure/store Robot

We export to the storage platform of your choice.

The /azure/store Robot exports encoding results to Microsoft Azure.

Parameters

Name Type Default Description
credentials (required) String Please create your associated Template Credentials in your Transloadit account and use the name of your Template Credentials as this parameter's value. They will contain the values for your Azure container, account and key. While we recommend to use Template Credentials at all times, some use cases demand dynamic credentials for which using Template Credentials with their static nature is too unwieldy. If you have this requirement, feel free to use the following parameters instead: "account", "key", "container".
path String "${unique_prefix}/${file.url_name}" The path at which the file is to be stored. This may include any available Assembly variables.
content_type String "" The content type with which to store the file. By default this will be guessed by Azure.
content_encoding String "" The content encoding with which to store the file. By default this will be guessed by Azure.
content_language String "" The content language with which to store the file. By default this will be guessed by Azure.
cache_control String "" The cache control header with which to store the file.
metadata String {} A JavaScript object containing a list of metadata to be set for this file on Azure, such as { FileURL: "${file.url_name}" }. This can also include any available Assembly variables.
sas_expires_in Integer / Null null Set this to a number to enable shared access signatures for your stored object. This reflects the number of seconds that the signature will be valid for once the object is stored. Enabling this will attach the shared access signature (SAS) to the result URL of your object.
sas_permissions String "" Set this to a combination of r (read), w (write) and d (delete) for your shared access signatures (SAS) permissions.

Live demos

Our /azure/store Robot can be used in combination with other Robots, to create powerful workflows unique to your use case.
Here are a few example scenarios, and the required Assembly Instructions to implement them.
You can also try demos of these examples right here, live on our website.

Store uploaded files in a Microsoft Azure container

{
  "steps": {
    ":original": {
      "robot": "/upload/handle"
    },
    "exported": {
      "use": [":original"],
      "robot": "/azure/store",
      "result": true,
      "credentials": "YOUR_CREDENTIALS"
    }
  }
}

Blog posts about our /azure/store Robot

Over the years we wrote the following posts about our /azure/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.