bigquery-data-transfer-service

Discovers and inspects BigQuery Data Transfer Service configurations for data ingestion pipelines.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill bigquery-data-transfer-service-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bigquery-data-transfer-service
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/bigquery-data-transfer-service
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill bigquery-data-transfer-service-yashyasik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When building data pipelines on Google Cloud, teams often don't know whether data ingestion is already handled by an existing BigQuery Data Transfer Service (DTS) configuration, leading to duplicate transfers or misconfigured pipelines. This Skill discovers existing DTS transfer configs, extracts their metadata, and guides the declarative provisioning of new transfers. ## Core Features & Use Cases - Transfer Discovery: Lists and inspects existing DTS transfer configurations in a target project and region using bq CLI commands. - Data Source Parameter Discovery: Runs a Python script against the BigQuery Data Transfer REST API to enumerate available data sources and their required parameters, including OAuth authorization URL generation for Google data sources. - Declarative Provisioning Enforcement: Ensures all new transfer configs are created via a deployment.yaml resource provisioning framework rather than imperative CLI commands, with mandatory user confirmation of parameters. - Run Verification: Triggers manual transfer runs and polls for completion with a 5-minute timeout rule before proceeding with downstream pipeline work. - Use Case: A data engineer asked to "ingest Google Ads data into BigQuery" uses this Skill to check for an existing transfer, discover required data source parameters, obtain OAuth authorization, and verify a successful run before building downstream transformations. ## Quick Start Ask the assistant to check whether a BigQuery Data Transfer Service config already exists for your data source in your GCP project and region before creating a new ingestion pipeline.

Frequently Asked Questions about bigquery-data-transfer-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for existing BigQuery Data Transfer Service configs?▼

Run bq ls --transfer_config with the target transfer location and project ID to list existing transfers in a region. Then use bq show --format=prettyjson --transfer_config with the resource name to extract full configuration details.

How do I find required parameters for a BigQuery DTS data source?▼

Query the BigQuery Data Transfer REST API dataSources endpoint for your project and region, or run the included bigquery_dts.py script with a data source ID. It returns all required parameters and generates an OAuth authorization URL for Google data sources.

Can I create BigQuery DTS transfers with bq mk or gcloud commands?▼

No, this workflow requires all new DTS configurations to be provisioned declaratively through a deployment.yaml resource provisioning framework. CLI commands are permitted only for discovery, listing, showing configs, and triggering manual transfer runs.

Does BigQuery DTS support OAuth authorization for Google data sources?▼

Yes, Google ecosystem sources like Google Ads and YouTube require OAuth when using end user credentials. The discovery script generates an authorization URL; after the user authorizes, the returned versionInfo code is set in deployment.yaml.

What happens if a BigQuery transfer run takes too long?▼

The workflow polls the transfer run every 30-60 seconds for up to 5 minutes. If still in progress after 5 minutes, it stops and asks the user to confirm when ingestion finishes before continuing with downstream pipeline tasks.