Schedule Runs
bigquery_data_transfer.schedule_runs
ActionGoogle Cloudconnection required
Calls BigQuery Data Transfer POST /v1/projects/{projectsId}/transferConfigs/{transferConfigsId}:scheduleRuns.
Creates transfer runs for a time range [start_time, end_time].
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
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
transfer_config Transfer config id. | string | Yes | — | — | — |
body Request body (ScheduleTransferRunsRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
runs | array | — |
{
"ok": false,
"runs": []
}Related Google BigQuery Data Transfer nodes
See Schedule Runs 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.