ActionAzure Blob StorageUpdated May 2026

How do I list Azure Blob Storage objects?

Short answer: Drop the "Azure Blob Storage → List Blobs in Container" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Azure Blob Storage actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Container container	string	Required	—
Prefix prefix	string	Optional	—

Sample request

{
  "container": "{{trigger.container}}",
  "prefix": "{{trigger.prefix}}"
}

Returns

{
  "EnumerationResults": {
    "Blobs": {
      "Blob": [
        {
          "Name": "file.txt",
          "Properties": {
            "Content-Length": "1024"
          }
        }
      ]
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Blobs in Container.

Any of these apps can fire this action as part of a workflow.

Gmail → Azure Blob Storage

1 Gmail triggers

Slack → Azure Blob Storage

13 Slack triggers

Google Sheets → Azure Blob Storage

2 Google Sheets triggers

HubSpot → Azure Blob Storage

18 HubSpot triggers

FAQ

Questions about List Blobs in Container.

What does the List Blobs in Container action do in Azure Blob Storage?

Returns paginated blobs within a container with optional prefix filter ("list all PDFs under invoices/2026/"). Useful for batch-processing workflows that need to discover all blobs matching a pattern.

What inputs does List Blobs in Container require?

Required: Container. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Azure Blob Storage returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Blobs in Container support batch operations?

Yes. Run List Blobs in Container inside a Loop node to process arrays. Tiny Command handles Azure Blob Storage's rate limits automatically so you don't have to throttle manually.

More actions