Azure Blob StorageInstall

Overview

The Azure Blob Storage node for n8n allows you to interact with Azure Blob Storage, specifically focusing on operations related to blobs within containers.
For the Blob → Upload Blob operation, this node uploads binary data from your workflow into a specified blob within an Azure storage container.

Common scenarios:

• Automating file uploads (e.g., images, documents) to Azure Blob Storage as part of a business process.
• Storing processed files or backups in the cloud.
• Integrating with other systems that require files to be uploaded to Azure Blob Storage.

Practical example:
You receive a PDF via email, process it in n8n, and then use this node to upload the PDF to a specific folder (blob path) in your Azure Blob Storage account.

Properties

Output

• The output is a JSON array containing the result of the upload operation for each input item.
• For each item, the output contains the response from Azure's upload API, which typically includes metadata such as ETag, last modified date, and request ID.
• No binary data is returned; only metadata about the upload operation is included in the output.

Example output structure:

[
  {
    "etag": "\"0x8DXXXXXXXXXXXX\"",
    "lastModified": "2024-06-01T12:34:56.789Z",
    "requestId": "12345678-0001-0023-45ab-cdef6789abcd",
    "version": "2020-10-02",
    "date": "2024-06-01T12:34:57.000Z"
    // ...other Azure response fields
  }
]

Dependencies

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

Troubleshooting

Common issues:

• Missing binary data:

  • Error: "No binary data exists on item!"
    Cause: The input item does not contain a binary property with the specified name.
    Solution: Ensure the previous node outputs binary data under the correct property name.

• Incorrect binary property name:

  • Error: "No binary data property \"<name>\" does not exists on item!"
    Cause: The specified binary property does not exist in the input item.
    Solution: Double-check the property name matches the one used in your workflow.

• Invalid credentials or permissions:

  • Error messages from Azure indicating authentication or authorization failures.
    Solution: Verify your Azure Storage connection string and ensure the account has write permissions to the target container.

• Container or blob name errors:

  • If the container does not exist or the blob name is invalid, Azure will return an error.
    Solution: Confirm the container exists and the blob name follows Azure naming conventions.

Links and References

• Azure Blob Storage documentation
• n8n Documentation: Credentials
• @azure/storage-blob npm package