Azure Blob StorageInstall

Overview

This node allows you to create a new container in Azure Blob Storage. Containers are fundamental storage units within Azure Blob Storage, used to organize and manage blobs (files). This operation is useful when you need to programmatically provision new containers for storing files, backups, logs, or other data types in your Azure cloud environment.

Common scenarios:

• Automating the setup of new storage areas for different projects or clients.
• Creating containers as part of a workflow that processes and stores uploaded files.
• Segregating data by creating separate containers for different data categories.

Example:
A company wants to automatically create a new container every time a new client is onboarded, ensuring their files are stored separately.

Properties

Output

The output is a JSON object containing information about the result of the container creation operation. Typical fields may include:

{
  "containerClient": { /* Azure SDK response object */ }
}

• The exact structure depends on the Azure SDK's create() method response, but it generally includes metadata about the newly created container.

Dependencies

• External Service: Requires access to an Azure Blob Storage account.
• Credentials: Needs an n8n credential named azureStorageApi with a valid Azure Storage connection string.
• npm Dependency: Uses the @azure/storage-blob package.

Troubleshooting

Common Issues:

• Container already exists: Attempting to create a container with a name that already exists will result in an error from Azure.
  • Resolution: Use a unique container name or handle the error gracefully.
• Invalid container name: Azure enforces naming rules (lowercase letters, numbers, and hyphens only).
  • Resolution: Ensure the container name meets Azure requirements.
• Authentication errors: Invalid or missing credentials will prevent the node from connecting to Azure.
  • Resolution: Verify the azureStorageApi credential and its connection string.

Error Messages:

• "No binary data exists on item!": Not relevant for this operation, but may appear if misconfigured.
• Azure-specific errors such as ContainerAlreadyExists or authentication failures will be passed through from the Azure SDK.

Links and References

• Azure Blob Storage documentation
• Azure Container Naming Rules
• n8n Documentation: Credentials