Azure Blob Storage

Overview

This node enables interaction with Azure Blob Storage, specifically managing containers and blobs within an Azure storage account. It supports operations such as creating, deleting, listing containers and blobs, uploading blob data, downloading blob content, and generating Shared Access Signatures (SAS) for secure delegated access.

The Get SAP operation under the Blob resource generates a time-limited SAS URL for a specified blob, allowing secure read access without exposing the primary storage keys. This is useful when you want to share or grant temporary access to a blob to external users or services securely.

Practical examples:

• Generating a SAS URL to provide temporary download access to a file stored in Azure Blob Storage.
• Automating blob uploads and then sharing access links via email or other communication channels.
• Managing container lifecycle by creating or deleting containers programmatically.

Properties

Output

The output for the Get SAP operation is a JSON object containing:

• blobUrlSAS: A string representing the full URL to the blob including the generated SAS token query parameters. This URL grants read permissions starting 5 minutes before the current time and expires after 24 hours.

Example output JSON:

{
  "blobUrlSAS": "https://<account>.blob.core.windows.net/<container>/<blob>?sv=...&sr=b&sp=r&se=...&st=...&sig=..."
}

This URL can be used directly to access the blob with the specified permissions and validity period.

Dependencies

• Requires an Azure Storage API connection string credential configured in n8n.
• Uses the official @azure/storage-blob npm package for interacting with Azure Blob Storage.
• The node expects valid Azure Storage account credentials with sufficient permissions to generate SAS tokens.

Troubleshooting

• Error: "La chaîne de connexion est indéfinie ou non fournie dans les credentials."
  This means the Azure Storage connection string is missing or not provided. Ensure that the API key credential is properly set up with a valid connection string.

• Error: "accountName ou accountKey est null"
  Indicates that the connection string does not contain the required AccountName or AccountKey parts. Verify the connection string format and completeness.

• No binary data exists on item! (for upload operations)
  Occurs if the input item lacks the expected binary property. Make sure the input data contains binary data under the specified property name.

• General permission errors
  If SAS generation or blob operations fail due to permissions, check that the Azure Storage account key has adequate rights and that the connection string is correct.

Links and References

• Azure Blob Storage documentation
• Shared Access Signature (SAS) overview
• @azure/storage-blob npm package