Poll Azure Blob / Datalake and POST every new file to your API
DocEvent checks a directory in your Azure Blob / Datalake storage (ADLS Gen2) on a schedule, collects new files and POSTs each one to your HTTP or HTTPS endpoint. Turn Azure storage into an API feed — retries, filtering and audit trail included.
From
Azure Blob / Datalake Pull
To
HTTP Webhook
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blob / Datalakepull
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 / Datalake Pull to HTTP Webhook routing works
Source
Azure Blob / Datalake
DocEvent checks a folder in your Azure Blob storage or Datalake (ADLS Gen2) on a schedule and collects new files.
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 / Datalake Pull
Scheduled polling of an Azure Datalake Storage Gen2 filesystem — the hierarchical namespace on Azure Blob Storage — using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
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 / Datalake Pull → HTTP Webhook channel.
- Ingest files landing in ADLS straight into your processing pipeline
- Feed microservices from Azure storage without Event Grid plumbing
- Forward partner drops in a Datalake directory to a REST API
- Collect analytics output from ADLS into downstream services
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 / Datalake Pull or HTTP Webhook side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Blob / Datalake
Scheduled polling of an Azure Datalake Storage Gen2 filesystem — the hierarchical namespace on Azure Blob Storage — using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks a folder in your Azure Blob storage or Datalake (ADLS Gen2) on a schedule and collects new files.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 sources to HTTP Webhook