ActionAzure Blob StorageUpdated September 2026
How do I delete an Azure Blob Storage object?
Short answer: You can delete blob in Azure Blob Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure Blob Storage Delete Blob action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 blob | string | Required | – |
Sample request
{"container": "{{trigger.container}}","blob": "{{trigger.blob}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete Blob.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete Blob.
What does the Delete Blob action do in Azure Blob Storage?
Removes a specific blob from a container. Irreversible. For workflows that need to clean up temporary blobs after processing (transcoded video files, scrap downloads, expired exports), this is the cleanup action.
What inputs does Delete Blob require?
Required: Container, Blob Name. 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 run history shows the failed step with its input and the error message Azure Blob Storage returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Delete Blob support batch operations?
Run Delete Blob inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Azure Blob Storage's rate limits.
More actions
Other Azure Blob Storage actions.
Action
List Blobs in Container
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.
ActionUpload Blob
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.