AZURE STORAGE n8n INTEGRATION: AUTOMATE AZURE STORAGE WITH N8N

This action retrieves multiple storage containers from your Azure Storage account in a single operation. It's your go-to action when you need to list what containers exist, audit your storage structure, or feed container information into subsequent workflow steps.

Key parameters:

• Credential to connect with: Select your Azure Storage credentials from the dropdown. This is required for authentication.
• Return All: Toggle this on to retrieve every container in your account, or leave it off to use the Limit parameter.
• Limit: When Return All is off, this number (default: 50) caps how many containers are returned. Accepts any positive integer.
• Options: Expandable section for additional configurations as needed.

Use cases:

• Generate a daily report of all containers and their metadata
• Feed container names into a loop that processes each one individually
• Audit your storage account to identify unused or legacy containers

This action is ideal when building workflows that need to operate across multiple containers or when you need to programmatically discover your storage structure.

This action permanently removes a storage container from your Azure Storage account. Use it with care—once deleted, the container and all its contents are gone.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: Specify the container to delete by ID. You can select from a dropdown or use an expression for dynamic selection. This is required.

Use cases:

• Automatically clean up temporary project containers after a deadline
• Remove staging containers once data has been migrated to production
• Implement a retention policy that deletes containers older than X days

Best practice: always add a confirmation step or logging node before this action in critical workflows to prevent accidental deletions.

This action creates a new storage container in your Azure Storage account. It's the foundation for any workflow that needs to organize files into new logical groupings.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container Name: Text field where you specify the name for your new container (required). Names must follow Azure's naming rules: lowercase letters, numbers, and hyphens only.

Use cases:

• Automatically create a new container for each new client or project
• Set up dated containers (e.g., "backup-2024-01") for organized archiving
• Generate temporary containers for batch processing jobs

💡 Pro tip: Combine this with the Create blob action to not only create containers but also populate them with initial files or templates in one workflow.

This action retrieves detailed information about a specific container from your Azure Storage account. Unlike "Get many," this targets one container precisely.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: Select the container by ID using the dropdown or an expression (required).
• Options: Additional configuration options if needed.

Use cases:

• Verify a container exists before attempting to upload blobs to it
• Retrieve container metadata for logging or reporting purposes
• Check container properties as a conditional step in your workflow

This action works well as a validation step—confirm the container is accessible before proceeding with blob operations.

This action creates a new blob (file) inside an Azure Storage container. It's essential for any workflow that needs to store data, documents, or files in the cloud.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: Select the target container from the dropdown (required).
• Blob Name: The name for your new blob, including any path structure like "folder/myfile.txt" (required).
• From: Specifies the data source—typically "Binary" for file uploads (required).
• Binary Contents: The actual binary data that will become the blob's contents (required).
• Options: Additional settings for advanced configurations.

Use cases:

• Save form submissions or webhook payloads as JSON files in Azure
• Back up generated reports or exported data automatically
• Store processed images or documents from upstream workflow steps

When dealing with files from other nodes (like HTTP Request or Read Binary File), map the binary data directly to this action for seamless uploads.

This action removes a specific blob from an Azure Storage container. Like container deletion, this is permanent—use it deliberately.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: The container holding the blob, selected by ID (required).
• Blob: The specific blob to delete, selected by ID (required). Both parameters support expressions for dynamic targeting.
• Options: Currently no additional properties, but available for future flexibility.

Use cases:

• Clean up temporary files after they've been processed
• Implement file expiration policies based on age or other criteria
• Remove outdated versions when a new file is uploaded

Consider logging deleted blob names before executing this action for audit trail purposes.

This action retrieves multiple blobs from a specific container. It's perfect for listing files, batch processing, or feeding blob information into loops.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: Select the container to list blobs from by ID (required).
• Return All: Toggle to retrieve every blob, or leave off to use Limit.
• Limit: Maximum blobs to return (default: 50). Accepts any positive integer.
• Options: Expandable for additional configurations.

Use cases:

• List all files in a container for processing or reporting
• Find blobs matching certain patterns for batch operations
• Monitor container contents and trigger actions when new blobs appear

This action pairs perfectly with n8n's loop functionality to process each blob individually in subsequent steps.

This action retrieves a specific blob from an Azure Storage container, including its contents. Use it when you know exactly which file you need.

Key parameters:

• Credential to connect with: Your Azure Storage credentials (required).
• Container: The container holding the blob, selected by ID (required).
• Blob: The specific blob to retrieve, selected by ID (required).
• Options: Additional configuration options as needed.

Use cases:

• Download a specific configuration file for use in your workflow
• Retrieve stored data to process, transform, or send elsewhere
• Access backup files for restoration or verification purposes

The retrieved blob data can be passed to other nodes for processing, sent via email, uploaded elsewhere, or used as input for transformations.