Google Cloud Storage Integration

Connect your Google Cloud Storage bucket to Alloy for automatic data ingestion. Alloy uses a GCS Transfer Job to pull data from your bucket into our ingestion pipeline.

How it works

Alloy sets up a Storage Transfer Service job that periodically syncs data from your GCS bucket into Alloy's ingestion bucket. Once files land, they're automatically processed into missions.

Setup

Share bucket access — grant read access on your GCS bucket to the Alloy service account (we'll provide the service account email)

Contact the Alloy team — provide your GCS bucket name

We configure the transfer job — Alloy creates a Storage Transfer Job that pulls new files from your bucket

The transfer job only copies new or changed files on each run — it won't re-process data that's already been ingested.

What to provide

Contact the Alloy team with:

GCS bucket name — e.g. gs://my-org-mission-data
Bucket region — for optimal transfer performance

We'll send you the service account email to grant access to, and handle the rest.

Pull frequency

Once your integration is set up, choose how often Alloy polls your bucket from Org settings → Integrations → Pull frequency. Options: 1 min, 5 min, 15 min, 30 min, 1 hour. Default is 5 min.

GCS LIST requests are very cheap (~$0.04 per million requests), so pull frequency on GCS has negligible cost impact even on large buckets. Pick whatever latency you need.

Folder structure and supported files

See Uploading your first mission for details on folder structure expectations, metadata.json format, and supported file types. These apply to all data ingestion methods including GCS.