Azure Blob Storage

Interact with Azure Blob Storage, containers and blobs.

Actions7

Container Actions
- Create Container
- Delete
Blob Actions

Overview

This node enables interaction with Azure Blob Storage, specifically allowing operations on storage containers and blobs. The "Upload Blob" operation under the "Blob" resource lets users upload binary data from n8n workflow items into an Azure Blob Storage container as a new blob.

Common scenarios include:

Automating file uploads to Azure Blob Storage from various sources.
Storing processed files or generated reports in Azure cloud storage.
Integrating Azure Blob Storage as part of a larger data pipeline for backup or archival.

For example, you might use this node to upload images received via webhook or generated PDFs directly into a specified Azure container, organizing them by folder paths within blob names.

Properties

Name	Meaning
Container Name	The name of the Azure storage container where the blob will be uploaded.
Blob Name	The name of the blob to create inside the container. Supports folder-like paths (e.g., `folder/file.txt`).
Binary Property	The name of the binary property in the input item that contains the data to upload.

Output

The node outputs an array of JSON objects representing the result of the upload operation for each item processed. Each output object corresponds to the response from Azure Blob Storage's upload method, which typically includes metadata about the uploaded blob such as ETag, last modified timestamp, and request ID.

No binary data is output by this node; it focuses on uploading binary data from input items rather than producing binary output.

Dependencies

Requires an Azure Storage API credential configured in n8n that provides a valid connection string for accessing Azure Blob Storage.
Uses the official @azure/storage-blob npm package internally to interact with Azure services.
No additional environment variables are needed beyond the configured credentials.

Troubleshooting

No binary data exists on item!
This error occurs if the specified binary property does not exist on the input item. Ensure the input data contains binary data under the exact property name provided in the "Binary Property" field.
No binary data property "[name]" does not exist on item!
Indicates a mismatch between the binary property name set in the node and the actual binary properties available on the input item. Double-check spelling and case sensitivity.
Credential or connection string issues
If the Azure Storage API credential is missing or invalid, the node will fail to connect. Verify that the credential contains a valid connection string with correct account name and key.
Blob name/path errors
Invalid blob names or paths may cause upload failures. Use valid characters and avoid unsupported patterns in blob names.