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 Blob → Delete operation, this node enables users to delete a specific blob (file or object) from a given container in their Azure Blob Storage account.

Common scenarios:

  • Automating cleanup of outdated or temporary files in cloud storage.
  • Removing sensitive data after processing.
  • Managing storage costs by deleting unused blobs.

Example use case:
After processing uploaded documents, automatically delete the original files from Azure Blob Storage to maintain compliance or save space.

Properties

Name Type Meaning
Container Name String The name of the storage container where the target blob resides.
Blob Name String The name (including path/folder structure if any) of the blob to be deleted from the container.

Output

The output is a JSON array containing the result of the delete operation for each input item.
For each deletion attempt, the output includes the response from Azure's deleteIfExists method, which typically contains information about whether the blob was found and deleted.

Example output:

[
  {
    "succeeded": true
  }
]
  • If the blob did not exist, "succeeded" may be false.

No binary data is produced by this operation.

Dependencies

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

Troubleshooting

Common issues:

  • Invalid credentials: If the Azure Storage connection string is incorrect or missing, authentication will fail.
  • Container or blob not found: If the specified container or blob does not exist, the operation will not throw an error but will return "succeeded": false.
  • Permission errors: The provided credentials must have permission to delete blobs in the specified container.

Error messages:

  • "No binary data exists on item!" – Not relevant for delete, but may appear if using upload/get operations incorrectly.
  • Azure SDK errors (e.g., authentication failures, network issues) will be surfaced as node errors in n8n.

How to resolve:

  • Double-check the container and blob names for typos.
  • Ensure the Azure credentials are correct and have sufficient permissions.
  • Verify network connectivity to Azure services.

Links and References

Discussion