Cloud & StorageReal-timeUpdated June 2026

Azure Blob Storage integration

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.

Connect Azure Blob Storage

No credit card required · Set up in under 2 minutes

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

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	Inputs	Open action
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.	2 inputs	View
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.	2 inputs	View
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.	4 inputs	View

Recipes

Pre-built Azure Blob Storage workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Azure Blob Storage → Slack alerts

AI-triage every Azure Blob Storage event, ping the right channel only when it matters.

Azure Blob Storage → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Azure Blob Storage → Notion database

Turn Azure Blob Storage into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

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.

No JSON to read

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.

FAQ

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?

Open the Tiny Command workflow builder, drop in a Azure Blob Storage node, and click Connect. Authorize Azure Blob Storage once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Azure Blob Storage triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Azure Blob Storage today. Use Tiny Command's universal Webhook or Schedule trigger to start Azure Blob Storage workflows, then run any Azure Blob Storage action you need.

What Azure Blob Storage actions can I run from a workflow?

3 Azure Blob Storage actions are available out of the box, covering cloud & storage operations like "Delete Blob". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Azure Blob Storage integration real-time?

Azure Blob Storage actions execute synchronously inside your workflow. Tiny Command waits for Azure Blob Storage's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Azure Blob Storage with Tiny Command?

No. Every Azure Blob Storage trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Azure Blob Storage API endpoint directly.

How much does the Azure Blob Storage integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Azure Blob Storage integration itself has no per-app surcharge.