Connect Notion to Azure Blob Storage in two minutes.
Real-time triggers from Notion, ready-made actions in Azure Blob Storage. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Notion.
- New Database ItemWebhook
- New PageWebhook
- Page UpdatedWebhook
Workflows do something in Azure Blob Storage, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Notion, do it in Azure Blob Storage.
3 Notion triggers wired to 3 Azure Blob Storage actions. Most-used pairing: New Database Item → Delete Blob.
Or fire it the other way around.
0 Azure Blob Storage triggers wired to 12 Notion actions downstream.
- Use any trigger in the catalog as the upstream.
Common Notion → Azure Blob Storage workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Connect Notion and Azure Blob Storage in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Notion and Azure Blob Storage
Open Tiny Command, authorize Notion and Azure Blob Storage once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Notion trigger
Drop the Notion → New Database Item trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/notion.trigger-database-item-added - 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 Azure Blob Storage action
Drop the Azure Blob Storage → Delete Blob action below it. Map fields from the Notion payload into the Azure Blob Storage inputs.
azure-blob.delete-blob - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Notion + Azure Blob Storage.
How long does it take to connect Notion and Azure Blob Storage on Tiny Command?
Is the Notion ↔ Azure Blob Storage integration real-time?
Can I filter or transform data between Notion and Azure Blob Storage?
What Notion events can trigger a Azure Blob Storage workflow?
Do I need a paid plan to use Notion with Azure Blob Storage?
What if I want Azure Blob Storage → Notion instead?
Other apps that pair well with Notion.
Wire Notion to Azure Blob Storage in 2 minutes.
Free tier available. No credit card. No onboarding call.
