Appearance
Azure Blob Storage
Manage containers and blobs in Azure Blob Storage.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://{account_name}.blob.core.windows.net |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | azure-blob |
Using Azure Blob Storage in a workflow
- Go to Connections and click New Connection.
- Pick Azure Blob Storage from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET / | List containers |
PUT /{container} | Create a container |
DELETE /{container} | Delete a container |
GET /{container} | List blobs in a container |
GET /{container}/{blob} | Download a blob |
PUT /{container}/{blob} | Upload a blob |
DELETE /{container}/{blob} | Delete a blob |
HEAD /{container}/{blob} | Get blob properties |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /
List containers
| Detail | Value |
|---|---|
| Operation ID | cloud.listContainers |
| Method | GET |
| Path | / |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listContainers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
PUT /{container}
Create a container
| Detail | Value |
|---|---|
| Operation ID | cloud.createContainer |
| Method | PUT |
| Path | /{container} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createContainer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
DELETE /{container}
Delete a container
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteContainer |
| Method | DELETE |
| Path | /{container} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteContainer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
GET /{container}
List blobs in a container
| Detail | Value |
|---|---|
| Operation ID | cloud.listBlobs |
| Method | GET |
| Path | /{container} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listBlobs. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
GET /{container}/{blob}
Download a blob
| Detail | Value |
|---|---|
| Operation ID | cloud.getBlob |
| Method | GET |
| Path | /{container}/{blob} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getBlob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
PUT /{container}/{blob}
Upload a blob
| Detail | Value |
|---|---|
| Operation ID | cloud.putBlob |
| Method | PUT |
| Path | /{container}/{blob} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.putBlob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
DELETE /{container}/{blob}
Delete a blob
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteBlob |
| Method | DELETE |
| Path | /{container}/{blob} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteBlob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.
HEAD /{container}/{blob}
Get blob properties
| Detail | Value |
|---|---|
| Operation ID | cloud.getBlobProperties |
| Method | HEAD |
| Path | /{container}/{blob} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure Blob Storage connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getBlobProperties. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Azure Blob Storage API reference.