Short answer: You can upload blob in Azure Blob Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure Blob Storage Upload Blob action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
{"container": "{{trigger.container}}","blob": "{{trigger.blob}}","content": "{{trigger.content}}","contentType": "{{trigger.contentType}}"}
{"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.
Any of these apps can fire this action as part of a workflow.