Connect Azure Blob Storage to Gmail in two minutes.
Real-time triggers from Azure Blob Storage, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Azure Blob Storage.
- Azure Blob Storage has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.
Workflows do something in Gmail, instantly.
- Add Labels to MessageAPI
- Create DraftAPI
- Create LabelAPI
- Delete DraftAPI
- Delete LabelAPI
- Delete MessageAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Azure Blob Storage, do it in Gmail.
0 Azure Blob Storage triggers wired to 27 Gmail actions.
Or fire it the other way around.
1 Gmail triggers wired to 3 Azure Blob Storage actions downstream.
See Gmail → Azure Blob Storage →Common Azure Blob Storage → Gmail workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Connect Azure Blob Storage and Gmail in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Azure Blob Storage and Gmail
Open TinyCommand, authorize Azure Blob Storage and Gmail once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Azure Blob Storage trigger
Drop the Azure Blob Storage → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/azure-blob.event - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Azure Blob Storage payload into the Gmail inputs.
google-gmail.add-labels - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.