Azure Blob Storage
Azure Blob Storage object actions
Azure Blob Storage is Microsoft's S3-equivalent object storage — used by Azure-native workloads for backups, media, data-lake landing zones, and static-site hosting. Tiny Command exposes three actions, no triggers (for event-driven workflows, Azure Blob Storage emits events to Event Grid which can dispatch via webhook to a Tiny Command webhook trigger URL — set this up in the Storage Account → Events section): Upload Blob (push a file from base64 content, text, or URL fetched server-side, with content-type and custom metadata), List Blobs (within a container, with optional prefix filter for "list all PDFs under invoices/2026/" patterns), Delete Blob. The connection uses an Azure Storage Account Name + Account Key (or a shared-access signature with appropriate permissions). The container scope matters — every blob lives in a container under the storage account; the connection plus container name plus blob name uniquely identify each object.
Do anything Azure Blob Storage can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Delete Blob | 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. |
| 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. |
| Upload 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. |
Pre-built Azure Blob Storage workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Azure Blob Storage event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Azure Blob Storage into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Azure Blob Storage once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Azure Blob Storage field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Azure Blob Storage integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Azure Blob Storage to Tiny Command?
What Azure Blob Storage triggers does Tiny Command support?
What Azure Blob Storage actions can I run from a workflow?
Is the Azure Blob Storage integration real-time?
Do I need to write code to use Azure Blob Storage with Tiny Command?
How much does the Azure Blob Storage integration cost?
More cloud & storage apps people connect.
Same category as Azure Blob Storage, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Azure Blob Storage.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
