Can HumDay connect to Google BigQuery?

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

Do I need to write code to automate Google BigQuery?

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 account.

What can HumDay do in Google BigQuery?

21 of the 36 documented operations change something in Google BigQuery, and 15 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google BigQuery 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 is held behind that approval.

Automate Google BigQuery

HumDay reads Google BigQuery’s own published API description and derives 36 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 is

A data platform for customers to create, manage, share and query data.

API host: bigquery.googleapis.com

What HumDay can do in Google BigQuery

21 documented operations change something in Google BigQuery.

POSTCreates a new empty dataset./projects/{projectId}/datasets
POSTStarts a new asynchronous job./projects/{projectId}/jobs
POSTRuns a BigQuery SQL query synchronously and returns query results if the query completes within a specified timeout./projects/{projectId}/queries
POSTGets the access control policy for a resource./{resource}:getIamPolicy
POSTSets the access control policy on the specified resource./{resource}:setIamPolicy
POSTCreates a new, empty table in the dataset./projects/{projectId}/datasets/{datasetId}/tables
POSTCreates a new routine in the dataset./projects/{projectId}/datasets/{datasetId}/routines
POSTReturns permissions that a caller has on the specified resource./{resource}:testIamPermissions
DELETEDeletes the dataset specified by the datasetId value./projects/{projectId}/datasets/{datasetId}
PATCHUpdates information in an existing dataset./projects/{projectId}/datasets/{datasetId}
PUTUpdates information in an existing dataset./projects/{projectId}/datasets/{datasetId}
POSTRequests that a job be cancelled./projects/{projectId}/jobs/{jobId}/cancel
DELETERequests the deletion of the metadata of a job./projects/{projectId}/jobs/{jobId}/delete
POSTStreams data into BigQuery one record at a time without needing to run a load job./projects/{projectId}/datasets/{datasetId}/tables/{tableId}/insertAll
DELETEDeletes the model specified by modelId from the dataset./projects/{projectId}/datasets/{datasetId}/models/{modelId}
PATCHPatch specific fields in the specified model./projects/{projectId}/datasets/{datasetId}/models/{modelId}
DELETEDeletes the table specified by tableId from the dataset./projects/{projectId}/datasets/{datasetId}/tables/{tableId}
PATCHUpdates information in an existing table./projects/{projectId}/datasets/{datasetId}/tables/{tableId}
PUTUpdates information in an existing table./projects/{projectId}/datasets/{datasetId}/tables/{tableId}
DELETEDeletes the routine specified by routineId from the dataset./projects/{projectId}/datasets/{datasetId}/routines/{routineId}
PUTUpdates information in an existing routine./projects/{projectId}/datasets/{datasetId}/routines/{routineId}

What HumDay can read from Google BigQuery

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

GETLists all projects to which you have been granted any project role./projects
GETReturns the email address of the service account for your project used for interactions with Google Cloud KMS./projects/{projectId}/serviceAccount
GETRetrieves the results of a query job./projects/{projectId}/queries/{jobId}
GETLists all jobs that you started in the specified project./projects/{projectId}/jobs
GETLists all datasets in the specified project to which you have been granted the READER dataset role./projects/{projectId}/datasets
GETReturns information about a specific job./projects/{projectId}/jobs/{jobId}
GETReturns the dataset specified by datasetID./projects/{projectId}/datasets/{datasetId}
GETLists all models in the specified dataset./projects/{projectId}/datasets/{datasetId}/models
GETLists all tables in the specified dataset./projects/{projectId}/datasets/{datasetId}/tables
GETLists all routines in the specified dataset./projects/{projectId}/datasets/{datasetId}/routines
GETRetrieves table data from a specified set of rows./projects/{projectId}/datasets/{datasetId}/tables/{tableId}/data
GETLists all row access policies on the specified table./projects/{projectId}/datasets/{datasetId}/tables/{tableId}/rowAccessPolicies
GETGets the specified model resource by model ID./projects/{projectId}/datasets/{datasetId}/models/{modelId}
GETGets the specified table resource by table ID./projects/{projectId}/datasets/{datasetId}/tables/{tableId}
GETGets the specified routine resource by routine ID./projects/{projectId}/datasets/{datasetId}/routines/{routineId}

How automating Google BigQuery 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 account.
Grant access, then go live. You approve the specific Google BigQuery operations it may use — and only those.