Azure Blob Storage icon

Azure Blob Storage

Interact with Azure Blob Storage, containers and blobs.
Join our community

Actions7

Overview

This node enables interaction with Azure Blob Storage, specifically managing containers and blobs within an Azure storage account. The "Get Many" operation under the "Blob" resource retrieves a list of blobs from a specified container. This is useful for scenarios where you want to enumerate all blobs in a container, such as listing files for processing, auditing storage contents, or dynamically generating file lists.

Practical example: You have a container storing daily reports as blobs, and you want to retrieve all blob names to process them further in your workflow.

Properties

Name Meaning
Container Name The name of the Azure storage container from which to list blobs.
Blob Name (Not used in "Get Many" operation) Generally the name of a specific blob; here not needed.

Note: For the "Get Many" operation on the "Blob" resource, only the Container Name property is relevant and required.

Output

The output is a JSON array where each item represents a blob object retrieved from the specified container. Each blob object contains metadata fields such as:

  • name: The blob's name.
  • deleted: Whether the blob is deleted.
  • snapshot: Snapshot identifier if applicable.
  • properties: An object containing detailed properties like:
    • lastModified
    • etag
    • contentLength
    • contentType
    • leaseStatus
    • leaseState
    • blobType
    • and other blob-specific metadata.

This output allows downstream nodes to access detailed information about each blob for further processing.

No binary data is output by this operation.

Dependencies

  • Requires an Azure Storage API credential configured in n8n that provides a valid connection string to the Azure Blob Storage account.
  • Uses the official Azure SDK package @azure/storage-blob internally to interact with the service.

Troubleshooting

  • Common issues:

    • Invalid or missing Azure Storage connection string credential will cause authentication failures.
    • Specifying a non-existent container name will result in empty results or errors depending on permissions.
    • Network connectivity issues can prevent listing blobs.

  • Error messages:

    • Errors related to missing or invalid credentials indicate the need to verify the Azure Storage API credential configuration.
    • Permission denied or authorization errors suggest the credential lacks sufficient rights to list blobs in the container.
    • If no blobs are returned, confirm the container exists and contains blobs.

Links and References

Discussion