Does Files.com connect to BigQuery through an API?

No. Files.com is not a BigQuery API connector, and it does not run SQL. It works the way BigQuery already loads data — through Google Cloud Storage. Files.com receives the files, prepares them, and places them in the GCS bucket your load job reads, then BigQuery loads them on your schedule.

Can Files.com send BigQuery exports back out to partners?

Yes. When BigQuery unloads query results to a GCS bucket, Files.com can pick them up and deliver them to partners over SFTP, as a secure share link, or to another cloud — with PGP encryption and a full audit trail of who received what.

Load Partner Files Into BigQuery

BigQuery loads from Google Cloud Storage and exports back to it. Files.com is the secure front door that collects partner files, converts them, and writes them into the GCS bucket BigQuery loads from — and delivers BigQuery exports back out to partners.

Start My Free Trial Contact Sales

How Files.com Fits With Google BigQuery

BigQuery loads data from files in Google Cloud Storage and unloads query results back to GCS. The hard part is rarely the load job — it is getting the right files into the bucket, on time, from partners and systems that send over SFTP in formats that vary by sender.

Files.com sits in front of the bucket. Partners and upstream systems send files to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates and routes each one, converts the format, and writes it into the GCS bucket BigQuery loads from — so the load job runs against clean data without a custom ingestion service. The same pattern runs in reverse: BigQuery unloads to GCS, and Files.com delivers those exports back out to partners.

What You Would Use

Receive Files Over Every Protocol

Partners and systems send to your Files.com site over SFTP, FTPS, FTP, or HTTPS. One endpoint, one set of credentials, full audit on every transfer.

See File Transfer

Write Straight Into GCS

An Automation watches for new arrivals and writes them into the Google Cloud Storage bucket your BigQuery load job reads — on a schedule or the moment a file lands.

See Automations

Convert Before Load

Convert CSV, JSON, XML, and EDI into the shape your load job expects, and pull values out of each file to route it, before BigQuery ever sees it.

See Transform & Extract

Mount The GCS Bucket

Connect your existing Google Cloud Storage bucket as a Files.com folder. Files land in place — no second copy, no data moved out of your cloud.

See Remote Servers

Files.com With Google BigQuery FAQ

Put Files.com In The File Path

Receive, transform, route, and audit every file moving to and from Google BigQuery — on one platform, with no server of your own to run.