Fetch from Google Cloud Storage

Fetch from Google Cloud Storage retrieves one or more objects from a GCS bucket and brings them into your Multi FileFeed (MFF) as input files. Use it to source files directly from buckets your team or partners already write to.

Availability: Requires the WorkflowsGcsFetch feature. Contact your OneSchema support representative if you do not see this transform.

What it does

• Input: source (no upstream input). This transform starts an MFF branch by connecting directly to Google Cloud Storage.
• Output: one file per selected object, in its original format.
• The transform connects using the configured storage account, retrieves the objects you select, and passes them downstream unchanged.

When to use it

• A partner system or internal job writes export files to a GCS bucket on a schedule.
• You want to avoid a manual download step before running files through OneSchema.
• You need to combine GCS-sourced files with files fetched from other connectors in the same MFF.

How to configure it

In the MFF builder, add a Fetch from Google Cloud Storage node as a source at the start of your MFF.

Settings

Configuration tips

• Confirm the connected storage account has read access to the bucket before saving the node.
• Each object is matched by its exact bucket and key.

Example

Setup

A nightly export job writes sales_export_2024-05-01.csv to a bucket at gs://acme-exports/daily/.

Output

The MFF receives the CSV file as an input file, ready for validation and delivery downstream.

Troubleshooting

"Object not found" errors

• Confirm the object key and bucket name are correct and that the file hasn't been moved or deleted.
• Check that the selected storage account still has valid credentials.

Wrong or unexpected files are fetched

• If multiple objects are selected, verify each object key matches the file you intend to pull.

See also

• Fetch from SFTP
• Push to S3
• Pull from Google Drive