ActionAzure Blob StorageUpdated May 2026

How do I upload a file to Azure Blob Storage?

Short answer: Drop the "Azure Blob Storage → Upload Blob" 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	—
Blob Name (path) blob	string	Required	—
File content (URL or raw bytes) content	string	Required	—
Content Type contentType	string	Optional	—

Sample request

{
  "container": "{{trigger.container}}",
  "blob": "{{trigger.blob}}",
  "content": "{{trigger.content}}",
  "contentType": "{{trigger.contentType}}"
}

Returns

{
  "url": "https://{{connection.accountName}}.blob.core.windows.net/{{inputs.container}}/{{inputs.blob}}",
  "etag": "etag_abc"
}

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

Triggered by

Apps that pair well as the trigger for Upload Blob.

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 Upload Blob.

What does the Upload Blob action do in Azure Blob Storage?

Uploads a blob from base64 content, text, or fetched URL with content-type and custom metadata. For files >100MB, the simple-shot upload caps out — use block-blob multipart uploads via HTTP action for larger files.

What inputs does Upload Blob require?

Required: Container, Blob Name (path), File content (URL or raw bytes). 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 Upload Blob support batch operations?

Yes. Run Upload Blob 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