Google BigQuery Reservation
Google CloudOAuth 2.0Connection test available
A service to modify your BigQuery reservations (Google OAuth2).
OCNORA ships 11 typed Google BigQuery Reservation operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google BigQuery Reservation
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google BigQuery Reservation
Operations, grouped by what they do to your data.
Create and send 2
Delete and cancel 2
Other operations 1
A sample Google BigQuery Reservation workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google BigQuery Reservation trigger is needed.
- 2Get Capacity Commitmentbigquery_reservation.get_capacity_commitmentReturns information about the capacity commitment.
- 3Create Capacity Commitmentbigquery_reservation.create_capacity_commitmentCreates a new capacity commitment resource.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Create Capacity CommitmentCreates a new capacity commitment resource.bigquery_reservation.create_capacity_commitment
- Create ReservationCreates a new reservation resource.bigquery_reservation.create_reservation
- Delete Capacity CommitmentDeletes a capacity commitment.bigquery_reservation.delete_capacity_commitment
- Delete ReservationDeletes a reservation.bigquery_reservation.delete_reservation
- Failover ReservationFail over a reservation to the secondary location.bigquery_reservation.failover_reservation
- Get Capacity CommitmentReturns information about the capacity commitment.bigquery_reservation.get_capacity_commitment
- Get ReservationReturns information about the reservation.bigquery_reservation.get_reservation
- List Capacity CommitmentsLists all the capacity commitments for the admin project.bigquery_reservation.list_capacity_commitments
- List ReservationsLists all the reservations for the project in the specified location.bigquery_reservation.list_reservations
- Update Capacity CommitmentUpdates an existing capacity commitment.bigquery_reservation.update_capacity_commitment
- Update ReservationUpdates an existing reservation resource.bigquery_reservation.update_reservation
Google BigQuery Reservation questions
- How does OCNORA authenticate with Google BigQuery Reservation?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google BigQuery Reservation?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google BigQuery Reservation operation I need is not listed?
- Where Google BigQuery Reservation has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google BigQuery Reservation?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google BigQuery Reservation calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google BigQuery Reservation workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.