Azure Blob Storage icon

Azure Blob Storage

Interact with Azure Blob Storage, containers and blobs.
Join our community

Actions6

Overview

This node allows you to interact with Azure Blob Storage containers within n8n workflows. Specifically, for the Container resource and the Delete operation, it enables automated deletion of a specified container in your Azure Blob Storage account. This is useful for managing storage resources, cleaning up unused containers, or automating lifecycle management tasks.

Practical examples:

  • Automatically delete temporary containers after processing files.
  • Clean up test environments by removing containers created during testing.
  • Integrate with other workflow steps to manage storage dynamically based on business logic.

Properties

Name Type Meaning
Container Name String The name of the Azure Blob Storage container to be deleted. This is required.

Output

The output is an array of JSON objects, each representing the result of the delete operation for a container. The structure typically includes metadata about the deletion response from Azure, but does not contain binary data.

Example output:

[
  {
    "requestId": "xxxx-xxxx-xxxx",
    "version": "2021-04-10",
    "date": "2024-06-01T12:34:56.789Z",
    "clientRequestId": "xxxx-xxxx-xxxx",
    "errorCode": null
  }
]

Note: The actual fields may vary depending on the Azure SDK's response.

Dependencies

  • Azure Blob Storage Account: You must have access to an Azure Storage account.
  • Credentials: The node requires azureStorageApi credentials, specifically a connection string for authentication.
  • n8n Configuration: Ensure that the Azure Storage API credentials are set up in n8n.

Troubleshooting

Common issues:

  • Invalid Container Name: If the specified container does not exist, Azure will return an error indicating the resource was not found.
  • Insufficient Permissions: If the provided credentials lack permission to delete containers, the operation will fail.
  • Credential Misconfiguration: An incorrect or expired connection string will prevent the node from connecting to Azure.

Error messages and resolutions:

  • "No credentials found": Make sure you have configured the Azure Storage API credentials in n8n.
  • "ResourceNotFound": Verify that the container name is correct and exists in your Azure account.
  • "AuthorizationFailure": Check that your credentials have sufficient permissions to delete containers.

Links and References

Discussion