Get started

Poll Azure Blob Storage and POST every new file to your API

DocEvent checks a folder in your Azure Blob container on a schedule, collects new files and POSTs each one to your HTTP or HTTPS endpoint. Turn standard Azure storage into an API feed — retries, filtering and audit trail included.
From
Azure Blob Pull
To
HTTP Webhook
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.

How Azure Blob Pull to HTTP Webhook routing works

Source

Azure Blob

DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
DocEvent Channel
routes · retries · logs
Destination

HTTP Webhook

Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
1

File arrives via Azure Blob Pull

Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
2

Channel routes it

DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3

Delivered to HTTP Webhook

Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.

Common use cases

Real workflows that teams automate with a Azure Blob Pull → HTTP Webhook channel.
  • Turn a blob container into a webhook feed for your application
  • Forward partner uploads to an internal ingestion API
  • Trigger downstream processing without writing Event Grid handlers
  • Bridge Azure storage to a SaaS endpoint that accepts file POSTs
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Azure Blob Pull or HTTP Webhook side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Azure Blob
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
Destination:
HTTP Webhook
Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages

Related channel integrations

Other destinations from Azure Blob Pull
Other sources to HTTP Webhook
View all 72 channel integrations

You focus on integration,
we'll focus on delivery.

Get started for free