Actions7
- Container Actions
- Blob Actions
Overview
This node allows interaction with Azure Blob Storage, specifically managing containers and blobs within an Azure Storage account. It supports operations such as creating and deleting containers, uploading, downloading, listing, and deleting blobs, and generating SAS tokens for secure access.
The Create Container operation creates a new container in the specified Azure Blob Storage account. This is useful when you want to organize blobs into separate logical groups or namespaces.
Practical examples:
- Automatically create a new container to store files related to a specific project or client.
- Set up containers dynamically based on workflow inputs to segregate data.
- Prepare storage structure before uploading blobs.
Properties
| Name | Meaning |
|---|---|
| Container Name | The name of the container to create. Must be unique within the storage account. |
Output
The output is a JSON array where each item corresponds to the result of the container creation request. For the Create Container operation, the output contains the response object from the Azure SDK's create() method on the container client. This typically includes metadata about the created container such as its URL and HTTP response details.
Example output snippet (conceptual):
[
{
"requestId": "some-request-id",
"date": "2024-06-01T12:00:00Z",
"version": "2020-10-02",
"containerName": "example-container"
}
]
No binary data is produced by this operation.
Dependencies
- Requires an Azure Storage account connection string credential configured in n8n.
- Uses the official Azure Storage Blob SDK (
@azure/storage-blob) internally. - The node depends on having valid credentials with permissions to create containers in the target Azure Storage account.
Troubleshooting
Common issues:
- Invalid or missing Azure Storage connection string credential will cause authentication failures.
- Attempting to create a container with a name that already exists will result in an error.
- Container names must follow Azure naming rules (lowercase letters, numbers, and hyphens; between 3 and 63 characters).
Error messages:
"The specified container already exists."— occurs if the container name is already taken. Use a different name or delete the existing container first.- Authentication errors indicating invalid credentials or insufficient permissions require checking the configured API key or connection string.
- Network or permission errors may occur if the Azure Storage account is unreachable or the credentials lack container creation rights.