Move SFTP, API, and webhook data into BigQuery

Couchdrop turns inbound file transfers into a direct ingestion path for BigQuery, helping teams move operational data into their warehouse without building a separate ETL layer.

Files can arrive in Couchdrop from sources such as cloud storage, SFTP and FTP servers, APIs, or inbound webhooks. From there, a Transfer Automation or File Action can use the BigQuery platform integration to stream structured or semi-structured file contents into a target BigQuery table.

Because Couchdrop needs to translate file contents into BigQuery rows, BigQuery is configured as a system integration rather than a standard virtual folder. During setup, you provide the destination table details and map the incoming file data to the schema BigQuery expects.

• Move structured and semi-structured file data into BigQuery tables
• Ingest files received through SFTP, FTP, cloud storage, APIs, or inbound webhooks
• Use BigQuery inside Couchdrop Transfer Automations and File Actions
• Map incoming file fields to the destination BigQuery table schema
• Stream file contents into your data warehouse for analysis
• Use service account credentials for secure Google Cloud authentication
• Reduce custom ETL work for recurring partner, customer, or application data feeds

1. Create or identify the BigQuery table you want Couchdrop to upload data into.
2. Collect the required table details, including the Google Cloud project ID, dataset name, and table name.
3. Create a Google service account in APIs & Services → Credentials, then generate and download the service credentials JSON file.
4. In Couchdrop, add a new system integration and select BigQuery.
5. Provide the BigQuery table details and service credentials JSON.
6. Click Add System Integration.
7. Create a Transfer Automation or File Action and choose BigQuery as the platform type.
8. Map the incoming file structure to the BigQuery table schema, then test the workflow with a representative file.