SHAREPOINT IN. GCS OUT. NO SCRIPTS.
Archive SharePoint documents into Google Cloud Storage
DocEvent checks a SharePoint document library on a schedule and delivers each new file into your Google Cloud Storage bucket. Staff keep working in Microsoft 365; the documents land in the bucket your pipelines and retention policies own.
From
SharePoint
To
GCS
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How SharePoint to GCS routing works
Source
SharePoint
DocEvent checks a SharePoint document library on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via SharePoint
Scheduled polling of a Microsoft 365 SharePoint document library through the Microsoft Graph API. Connect your Microsoft account once from the console — the connection is reusable across endpoints and no secret is stored on the endpoint itself — then choose the site, library and folder. 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 GCS
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Common use cases
Real workflows that teams automate with a SharePoint → GCS channel.
- Archive Microsoft 365 libraries into object storage you control
- Feed Document AI or BigQuery pipelines from documents staff save in SharePoint
- Land approved documents in a Google Cloud data lake automatically
- Keep a retention copy outside the Microsoft 365 tenant
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SharePoint or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SharePoint
Scheduled polling of a Microsoft 365 SharePoint document library through the Microsoft Graph API. Connect your Microsoft account once from the console — the connection is reusable across endpoints and no secret is stored on the endpoint itself — then choose the site, library and folder. Filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks a SharePoint document library on a schedule and collects new files.Destination:
Google Cloud Storage
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Files are delivered into your Google Cloud Storage bucket.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