Short answer: Drop the "Azure Blob Storage → Upload Blob" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.