Get started

Poll Google Cloud Storage and POST every new file to your API

DocEvent checks your Google Cloud Storage bucket on a schedule, collects new files and POSTs each one to your HTTP or HTTPS endpoint. Turn any GCS bucket into an API feed — retries, filtering and audit trail included.
From
GCS Blob 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 GCS Blob Pull to HTTP Webhook routing works

Source

Google Cloud Storage

DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.
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 GCS Blob Pull

Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
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 GCS Blob Pull → HTTP Webhook channel.
  • Ingest files landing in GCS straight into your processing pipeline
  • Feed microservices from buckets without wiring Pub/Sub notifications
  • Forward partner drops in Google Cloud Storage to a REST API
  • Replace scheduled gsutil-download-and-POST scripts
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the GCS Blob Pull or HTTP Webhook side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Google Cloud Storage
Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.
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 GCS Blob Pull
Other sources to HTTP Webhook
View all 66 channel integrations

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

Get started for free