Azure Blob: Put Node

The Azure Blob: Put Node allows a workflow to upload a file into an Azure Blob Storage container.

Node Properties

There are several configuration parameters for the Azure Blob: Put Node …

Credential Configuration

There are two options for configuring credentials:

Service Credential

Select an account key previously saved in Losant as an Azure service credential. Note: This option is not available in Edge Workflows.

Direct Input of Azure Credentials

There are two parts to directly configuring credentials, and both of them are templatable:

• Account Name (Required)
• Account Key (Required)

We recommend that you create an account key specifically for use in Losant workflows (keys that only have access to the proper Azure Blob container).

We also recommend that you store these values as workflow globals or service credentials.

Blob Configuration

Next is to configure the fields required by Azure Blob Storage. All applicable fields are templatable:

• Container Name: (Required) The name of the container within the configured storage account.

• Blob Name: (Required) The name of the blob to upload, including the extension. If you wish to upload the file to a subdirectory within the container, the path should be included in this field. (e.g. “path/to/my/file.ext”)

  • Note: A leading slash (i.e. a subdirectory path beginning with ”/”) will cause Azure to create a directory with no name. Therefore, we do not recommend starting your directory with a leading slash.
• Blob Encoding: (Required) The encoding of the data being uploading. Defaults to UTF-8.
• Content Type: (Required) MIME type of the data being uploaded.

Note: It is currently only possible to upload content as a block blob.

Blob Contents

There are two different ways to input the contents of your blob. Both are templatable:

• Blob Content: The content of the blob to upload. If left blank, your configured blob will be uploaded without any content.

• Blob URL: (Required) The URL where the blob you wish to upload can be found. This option is useful when using the Temporary URL Output option in a notebook.

Output

The success or failure of the operation can optionally be placed at the specified payload path. If the operation fails, the result object will contain an error key in addition to the success state.

Node Example

The following is an example of a successful operation:

{
  "success": true
}

Node Errors

The following is an example of a failed operation:

{
  "success": false,
  "error": "Access Denied"
}

Related Nodes

• Azure Blob: Get