Connector
BigQuery
Read and write Google BigQuery over its REST API. There is no driver to install, and the builder shows a query's columns AND what it will cost before you run it.
Settings
What the connection form asks for. Every connection has a Staging side, which it needs, and an optional Production side with values of its own; both ask for the same settings.
| Project ID | The project jobs run under, which is what gets billed for a query. |
| Default dataset | Optional default for unqualified table names (e.g. analytics); a node can still address any dataset. |
| Location | The dataset's region, e.g. US, EU or europe-west4. Leave blank only for US datasets. |
| Endpoint (optional) | Set only for a private/VPC-SC endpoint. Blank uses Google's standard API. |
| Service Account JSON | Paste the whole downloaded key file. It needs BigQuery Job User plus read (or write) access to the datasets you'll use. Stored encrypted, and never shown again after you save it. |
Testing the connection
Test dry-runs SELECT 1: nothing runs and nothing is scanned, and it still proves the project, the key and the endpoint all work.
Good to know
- The builder shows a query's columns, and how much data it would scan, before you run it. Both come from the same dry run.
- The project you name is the one billed for queries.