Can HumDay connect to Google BigQuery Reservation?

Yes. HumDay reads Google BigQuery Reservation'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 Reservation?

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

What can HumDay do in Google BigQuery Reservation?

8 of the 13 documented operations change something in Google BigQuery Reservation, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google BigQuery Reservation

HumDay reads Google BigQuery Reservation’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 Reservation is

A service to modify your BigQuery flat-rate reservations.

API host: bigqueryreservation.googleapis.com

What HumDay can do in Google BigQuery Reservation

8 documented operations change something in Google BigQuery Reservation.

POSTCreates a new reservation resource./v1beta1/{parent}/reservations
POSTCreates a new capacity commitment resource./v1beta1/{parent}/capacityCommitments
POSTMoves an assignment under a new reservation./v1beta1/{name}:move
POSTCreates an assignment object which allows the given project to submit jobs of a certain type using slots from the specified reservation./v1beta1/{parent}/assignments
DELETEDeletes a assignment. No expansion will happen. Example: Organization organizationA contains two projects, project1 and project2. Reservation res1 exists and was created previousl…/v1beta1/{name}
PATCHUpdates an existing assignment./v1beta1/{name}
POSTSplits capacity commitment to two commitments of the same plan and commitmentendtime./v1beta1/{name}:split
POSTMerges capacity commitments of the same plan into a single commitment./v1beta1/{parent}/capacityCommitments:merge

What HumDay can read from Google BigQuery Reservation

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

GETReturns information about the reservation./v1beta1/{name}
GETLooks up assignments for a specified resource for a particular region./v1beta1/{parent}:searchAssignments
GETLists assignments. Only explicitly created assignments will be returned. Example: Organization organizationA contains two projects, project1 and project2. Reservation res1 exists…/v1beta1/{parent}/assignments
GETLists all the reservations for the project in the specified location./v1beta1/{parent}/reservations
GETLists all the capacity commitments for the admin project./v1beta1/{parent}/capacityCommitments

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