Azure Blob Storage icon

Azure Blob Storage

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

Actions6

Overview

The Azure Blob Storage node for n8n allows you to interact with Azure Blob Storage resources, specifically containers and blobs.
For the selected Resource: Blob and Operation: Get Many, this node retrieves a list of all blobs within a specified storage container in your Azure account.

Common scenarios:

  • Listing all files (blobs) stored in a particular Azure Blob Storage container.
  • Automating workflows that need to process or audit the contents of cloud storage.
  • Integrating with other systems by fetching file metadata from Azure Blob Storage.

Practical example:
You could use this node to fetch all blobs in a container and then loop over them to download, analyze, or move files as part of an automated workflow.

Properties

Name Type Meaning
Container Name String The name of the Azure Blob Storage container whose blobs you want to list. This is required.

Output

The node outputs an array of objects, each representing a blob found in the specified container.
Each object contains metadata about a blob, such as:

{
  "name": "example.txt",
  "deleted": false,
  "snapshot": "",
  "versionId": null,
  "isCurrentVersion": true,
  "properties": {
    "lastModified": "2023-12-01T12:34:56.000Z",
    "etag": "\"0x8D123456789ABC\"",
    "contentLength": 1024,
    "contentType": "text/plain",
    // ...other Azure blob properties
  },
  "metadata": {}
}
  • name: The name of the blob (file).
  • properties: An object containing various details such as last modified date, size, content type, etc.
  • metadata: Any custom metadata associated with the blob.

Note: The exact fields may vary depending on the Azure SDK version and the blob's attributes.

Dependencies

  • External Service: Requires access to an Azure Blob Storage account.
  • Credentials: You must configure the azureStorageApi credential in n8n, which should include a valid Azure Storage connection string.
  • npm Dependency: Uses the @azure/storage-blob package (bundled with the node).

Troubleshooting

Common issues:

  • Invalid credentials: If the Azure Storage connection string is incorrect or missing, authentication will fail.
  • Container not found: If the specified container does not exist, no blobs will be returned, or an error may occur.
  • Network errors: Connectivity issues between n8n and Azure can cause failures.

Error messages and resolutions:

  • "No binary data exists on item!": Not relevant for "Get Many" operation, but may appear if using upload/download operations without proper binary input.
  • Authentication errors: Ensure your Azure credentials are correct and have sufficient permissions.
  • Permission denied: Make sure the Azure Storage account key or SAS token has at least read/list permissions for the container.

Links and References

Discussion