Google BigQuery Data Transfer
Schedule queries or transfer external data from SaaS applications to Google BigQuery on a regular basis (Google OAuth2).
OCNORA ships 8 typed Google BigQuery Data Transfer operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google BigQuery Data Transfer
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google BigQuery Data Transfer
Operations, grouped by what they do to your data.
Create and send 2
Update 1
Delete and cancel 1
A sample Google BigQuery Data Transfer workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google BigQuery Data Transfer trigger is needed.
- 2Get Data Sourcebigquery_data_transfer.get_data_sourceRetrieves a supported data source and returns its settings.
- 3Create Transfer Configbigquery_data_transfer.create_transfer_configCreates a new data transfer configuration.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Create Transfer ConfigCreates a new data transfer configuration.bigquery_data_transfer.create_transfer_config
- Delete Transfer ConfigDeletes a data transfer configuration, including any associated transfer runs and logs.bigquery_data_transfer.delete_transfer_config
- Get Data SourceRetrieves a supported data source and returns its settings.bigquery_data_transfer.get_data_source
- Get Transfer ConfigReturns information about a data transfer config.bigquery_data_transfer.get_transfer_config
- List Data SourcesLists supported data sources and returns their settings.bigquery_data_transfer.list_data_sources
- List Transfer ConfigsReturns information about all transfer configs owned by a project in the specified location.bigquery_data_transfer.list_transfer_configs
- Schedule RunsCreates transfer runs for a time range [start_time, end_time].bigquery_data_transfer.schedule_runs
- Update Transfer ConfigUpdates a data transfer configuration.bigquery_data_transfer.update_transfer_config
Google BigQuery Data Transfer questions
- How does OCNORA authenticate with Google BigQuery Data Transfer?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google BigQuery Data Transfer?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google BigQuery Data Transfer operation I need is not listed?
- Where Google BigQuery Data Transfer has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google BigQuery Data Transfer?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google BigQuery Data Transfer calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google BigQuery Data Transfer workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.