Create Transfer Config

bigquery_data_transfer.create_transfer_config
ActionGoogle Cloudconnection required

Calls bigquerydatatransfer v1 POST /v1/projects/{projectsId}/transferConfigs.

Creates a new data transfer configuration.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google BigQuery Data Transfer
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
body
The TransferConfig resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
dataRefreshWindowDays
integer—
dataSourceId
string—
datasetRegion
string—
destinationDatasetId
string—
disabled
boolean—
displayName
string—
emailPreferences
object—
encryptionConfiguration
object—
error
object—
managedTableType
string—
metadataDestination
object—
name
string—
nextRunTime
string—
notificationPubsubTopic
string—
ownerInfo
object—
params
object—
schedule
string—
scheduleOptions
object—
scheduleOptionsV2
object—
state
string—
updateTime
string—
userId
string—
{
  "dataRefreshWindowDays": 0,
  "dataSourceId": "",
  "datasetRegion": "",
  "destinationDatasetId": "",
  "disabled": false,
  "displayName": "",
  "emailPreferences": {},
  "encryptionConfiguration": {},
  "error": {},
  "managedTableType": "",
  "metadataDestination": {},
  "name": "",
  "nextRunTime": "",
  "notificationPubsubTopic": "",
  "ownerInfo": {},
  "params": {},
  "schedule": "",
  "scheduleOptions": {},
  "scheduleOptionsV2": {},
  "state": "",
  "updateTime": "",
  "userId": ""
}

See Create Transfer Config run in a workflow.

In a technical demo we add the Google BigQuery Data Transfer connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.