Overview
This node enables interaction with Azure Blob Storage specifically for file resources. The Delete operation allows users to delete a specified blob (file) from a chosen Azure Blob Storage container. This is useful in scenarios where you want to programmatically remove files that are no longer needed, such as cleaning up temporary files, removing outdated backups, or managing storage costs by deleting unused blobs.
Practical example:
You have an automated workflow that processes images uploaded to Azure Blob Storage. After processing, the original images need to be deleted to free up space. Using this node's Delete operation, you can specify the container and blob name to remove those images automatically.
Properties
| Name | Meaning |
|---|---|
| Container Name | The name of the Azure Blob Storage container where the blob to delete resides. |
| Blob Name | The exact name of the blob (file) within the container that you want to delete. |
Output
The output JSON object for each deleted blob contains:
blobName: The name of the deleted blob.containerName: The container from which the blob was deleted.deleted: A boolean indicating successful deletion (true).requestId: The request identifier returned by Azure for the delete operation.
No binary data is output by this operation since it only confirms deletion.
Example output JSON:
{
"blobName": "example.txt",
"containerName": "my-container",
"deleted": true,
"requestId": "some-request-id"
}
Dependencies
- Requires an API authentication token or credentials to access Azure Blob Storage. Supported authentication methods include connection string, account key, or SAS token.
- The node uses the official Azure Storage Blob SDK internally.
- The user must configure the node with valid Azure Blob Storage credentials.
- The container specified must exist in the Azure Blob Storage account.
Troubleshooting
Error: Blob "X" does not exist
This occurs if the specified blob name is not found in the container. Verify the blob name spelling and container name.Invalid authentication method
Indicates misconfiguration of credentials. Ensure the provided credentials use one of the supported authentication methods.Failed to create Azure Blob Service Client
Usually caused by invalid or incomplete credentials. Double-check your Azure credentials and permissions.Permission denied or authorization errors
Make sure the API key or token has sufficient permissions to delete blobs in the specified container.Blob already deleted or concurrent modification
If the blob was deleted outside the workflow or concurrently, the node will throw an error. Handle such cases with "Continue on Fail" enabled if needed.