Azure Storage n8n integrationAutomate Azure Storage with n8n.
Where do the files your workflows keep asking for actually live? The Azure Storage n8n integration answers that with 8 operations across 2 resources, blobs and containers. No trigger ships with this node, so a Schedule Trigger or a Webhook starts the run. Built for teams moving files without writing scripts.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Azure Storage n8n integration actually do?
It gives a workflow direct access to an Azure Storage account without any code. The node covers 2 resources: blobs, which are the stored files themselves, and containers, which are the buckets that hold them. Across those two resources sit 8 operations, split evenly: create, delete, get and list, once for blobs and once for containers.
Take a nightly archive. A Schedule Trigger fires, container.getAll lists the containers on the account, blob.getAll walks the files inside each one, and blob.get pulls down the ones that matter. Pipe the result into Google Drive for a second copy, or log every filename into Google Sheets so someone can actually audit what was archived.
Second pattern: storing what an AI step produces. An image generator returns a URL, or an upstream node hands over a binary file. Either way blob.create writes it, because its From field accepts both a binary input and a URL. The workflow then posts the container and blob name into Slack so the team sees the asset the moment it exists.
Third pattern: giving each client its own space. container.create makes the container when a new account is signed up, blob.create drops documents into it as they arrive, and container.delete clears the whole thing at the end of the contract. Pair it with a row in Postgres that records which container belongs to which client, and the mapping never lives in someone's head.
When an Azure Storage call falls outside those 8 operations, the HTTP Request node covers it. It hits any endpoint of the API and reuses the same credential through predefined authentication, so nothing has to be re-authorized. That is the standard escape hatch in n8n, and it is worth knowing about before you assume something cannot be done.
One structural point to plan around: this node has no trigger of its own. Nothing in Azure Storage pushes an event into n8n. A workflow that touches it always starts somewhere else, most often on a Schedule Trigger running at a fixed interval, sometimes on a Webhook called by another service, sometimes on the trigger of another tool entirely. If that shape is new to you, the n8n training walks through it.
How do you connect Azure Storage to n8n?
- 01
Pick an authentication method
Open the Credentials menu in n8n and create an Azure Storage credential. Two methods are supported: OAuth2 (
oAuth2), where a Microsoft account grants n8n access, and Shared Key (sharedKey). A credential is created once and reused by every workflow after that, and the node offers it in a dropdown. You need a Microsoft Azure account and at least one user account with access to the service. - 02
Register an application with Microsoft
For OAuth2 on a self-hosted instance, open the Microsoft Application Registration Portal and select Register an application. Give it a Name, and under Supported account types choose any organizational directory plus personal Microsoft accounts. Copy the OAuth Callback URL from your n8n credential into the Redirect URI field, then select Web as the platform. Register, then copy the Application (client) ID into the n8n Client ID field.
- 03
Generate a client secret and connect
On the application page, go to Certificates & secrets and select + New client secret. Add a Description such as
n8n credential, confirm, then copy the value from the Value column straight away and paste it into n8n as the Client Secret. Back in n8n, hit Connect my account, log in to the Microsoft account and allow the app to access your info. The credential turns green and every Azure Storage node can select it.
The 8 operations the node runs
The Azure Storage node exposes 8 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Blob
4 operationsCreate blob
blob.createWhat you see in n8n
Notes & use cases
Writes a new file into a container, or replaces one that is already there under the same name.
Key parameters
- Container: the container to write into, picked from the list or passed as an expression such as
{{ $json.container }}. - Blob Name: the name the file gets in Azure, for example
myblob. - From: either
binary, which takes the file from an input field named in Binary Contents, orurl, which makes n8n fetch the contents from the address in URL. - Options: 20 extra fields, including Content Type, Access Tier, Blob Type and Tags.
Delete blob
blob.deleteWhat you see in n8n
Notes & use cases
Removes one existing file from a container. The container itself and everything else in it stay untouched.
Key parameters
- Container: where the file currently sits.
- Blob: the file to remove, selected from the list or resolved from an earlier node.
- Lease ID: an option, required when the blob has an active lease. Without it the call fails on a leased file.
Get blob
blob.getWhat you see in n8n
Notes & use cases
Retrieves the data for one specific file, so the workflow can pass it to the next node.
Key parameters
- Container: the container holding the file.
- Blob: the file to fetch.
- Simplify: an option that returns a trimmed version of the response instead of the raw payload, which keeps the item readable while you build.
- UPN: another option, turning Microsoft Entra object IDs in the response into User Principal Names.
Get many blobs
blob.getAllWhat you see in n8n
Notes & use cases
Lists the files inside one container, one n8n item per blob.
Key parameters
- Container: the only required field, since the listing is scoped to a single container.
- Return All: on, n8n pages through the API until every file has been returned; off, Limit caps how many come back.
- Fields: adds data to the output, such as
metadata,tags,versionsorsnapshots. - Filter: narrows the listing to
files,directoriesordeletedentries.
Container
4 operationsCreate container
container.createWhat you see in n8n
Notes & use cases
Sets up a new container on the storage account, ready to receive blobs.
Key parameters
- Container Name: the name of the new container, for example
mycontainer. - Access Level: an option with three values.
bloballows anonymous reads of blob data but no listing,containerallows anonymous reads and listing of blobs inside it, and Private keeps the data to the account owner. - Metadata: name and value pairs attached to the container itself.
Delete container
container.deleteWhat you see in n8n
Notes & use cases
Drops a container from the storage account. This is the destructive one, since the container is the level above the files.
Key parameters
- Container: the container to delete, selected from the list or passed in from an earlier step. It is the only field the operation takes, and no options collection comes with it.
Get container
container.getWhat you see in n8n
Notes & use cases
Reads the data for one named container, without touching what is inside it.
Key parameters
- Container: the container to read.
- Simplify: an option returning a simplified response rather than the raw data, handy when the next node only needs a couple of values.
Get many container
container.getAllWhat you see in n8n
Notes & use cases
Lists the containers on the storage account. No field is required, so it runs as an inventory step on its own.
Key parameters
- Return All: on, every container comes back; off, Limit sets the maximum number of items.
- Filter: keeps only containers whose name starts with a given prefix, such as
mycontainer. - Fields: adds
metadata,deletedorsystemdata to the output.
Need help automating Azure Storage with n8n?
A person reads every message.
