Azure Blob Storage

Overview

This node enables interaction with Azure Blob Storage, specifically allowing operations on storage containers and blobs. For the Blob - Get operation, it retrieves the content and metadata of a specified blob from a given container in Azure Blob Storage.

Common scenarios where this node is useful include:

• Downloading files stored in Azure Blob Storage for further processing or analysis.
• Accessing blob metadata such as content type, size, and modification dates.
• Integrating Azure Blob Storage data retrieval into automated workflows.

For example, you might use this node to fetch an image file stored as a blob, process it in subsequent workflow steps, or archive documents by retrieving their contents.

Properties

Output

The output is an array of items, each containing:

• json: Metadata about the retrieved blob, including:

  • blobName: The name of the blob.
  • blobType: Type of the blob.
  • contentEncoding: Encoding used for the blob content.
  • contentLanguage: Language of the blob content.
  • contentLength: Size of the blob in bytes.
  • contentType: MIME type of the blob.
  • lastAccessed: Timestamp of last access.
  • lastModified: Timestamp of last modification.
  • leaseDuration, leaseState, leaseStatus: Lease information if applicable.

• binary: Contains the actual blob data under the property data. This binary data includes the raw content of the blob and its MIME type.

This structure allows downstream nodes to access both the blob's content and its metadata conveniently.

Dependencies

• Requires an API authentication token or connection string credential for Azure Storage with permissions to read blobs.
• Uses the official Azure Storage Blob SDK (@azure/storage-blob) internally.
• The node expects the Azure Storage connection string to be configured securely in n8n credentials.

Troubleshooting

• Error: "No binary data exists on item!"
  Occurs if attempting to upload a blob but no binary data is present on the input item. Ensure that the input contains valid binary data before using upload operations.

• Error related to missing or invalid connection string
  The node requires a valid Azure Storage connection string. Verify that the credential is correctly set up and contains the necessary account name and key.

• Blob not found or access denied errors
  Confirm that the container and blob names are correct and that the API key has sufficient permissions to read blobs.

• Timeouts or network errors
  Check network connectivity to Azure services and ensure no firewall or proxy blocks the requests.

Links and References

• Azure Blob Storage Documentation
• Azure Storage Blob SDK for JavaScript
• n8n Documentation on Credentials