Can HumDay connect to Google BigQuery Data Transfer?

Yes. HumDay reads Google BigQuery Data Transfer's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.

Do I need to write code to automate Google BigQuery Data Transfer?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google BigQuery Data Transfer account.

What can HumDay do in Google BigQuery Data Transfer?

7 of the 13 documented operations change something in Google BigQuery Data Transfer, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google BigQuery Data Transfer account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google BigQuery Data Transfer is held behind that approval.

Automate Google BigQuery Data Transfer

HumDay reads Google BigQuery Data Transfer’s own published API description and derives 13 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google BigQuery Data Transfer is

Schedule queries or transfer external data from SaaS applications to Google BigQuery on a regular basis.

API host: bigquerydatatransfer.googleapis.com

What HumDay can do in Google BigQuery Data Transfer

7 documented operations change something in Google BigQuery Data Transfer.

POSTCreates a new data transfer configuration./v1/{parent}/transferConfigs
POSTCreates transfer runs for a time range [starttime, endtime]./v1/{parent}:scheduleRuns
POSTReturns true if valid credentials exist for the given data source and requesting user./v1/{name}:checkValidCreds
POSTEnroll data sources in a user project./v1/{name}:enrollDataSources
DELETEDeletes the specified transfer run./v1/{name}
PATCHUpdates a data transfer configuration./v1/{name}
POSTStart manual transfer runs to be executed now with scheduletime equal to current time./v1/{parent}:startManualRuns

What HumDay can read from Google BigQuery Data Transfer

These are the operations a schedule or a trigger can watch.

GETReturns log messages for the transfer run./v1/{parent}/transferLogs
GETReturns information about the particular transfer run./v1/{name}
GETReturns information about running and completed transfer runs./v1/{parent}/runs
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists supported data sources and returns their settings./v1/{parent}/dataSources
GETReturns information about all transfer configs owned by a project in the specified location./v1/{parent}/transferConfigs

How automating Google BigQuery Data Transfer works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google BigQuery Data Transfer account.
Grant access, then go live. You approve the specific Google BigQuery Data Transfer operations it may use — and only those.