Appearance
Google BigQuery
Run SQL queries and manage datasets and tables in Google BigQuery.
| Detail | Value |
|---|---|
| Category | Database |
| Base URL | https://bigquery.googleapis.com/bigquery/v2 |
| Authentication | See connector docs |
| Endpoints | 8 |
| Connector key | gcp-bigquery |
Using Google BigQuery in a workflow
- Go to Connections and click New Connection.
- Pick Google BigQuery from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /projects/{projectId}/datasets | List datasets |
POST /projects/{projectId}/datasets | Create a dataset |
GET /projects/{projectId}/datasets/{datasetId}/tables | List tables |
POST /projects/{projectId}/queries | Run a SQL query |
GET /projects/{projectId}/jobs | List jobs |
GET /projects/{projectId}/jobs/{jobId} | Get job details |
POST /projects/{projectId}/jobs/{jobId}/cancel | Cancel a job |
GET /projects/{projectId}/datasets/{datasetId}/tables/{tableId}/data | List table data |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /projects/{projectId}/datasets
List datasets
| Detail | Value |
|---|---|
| Operation ID | database.listDatasets |
| Method | GET |
| Path | /projects/{projectId}/datasets |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.listDatasets. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
POST /projects/{projectId}/datasets
Create a dataset
| Detail | Value |
|---|---|
| Operation ID | database.insertDataset |
| Method | POST |
| Path | /projects/{projectId}/datasets |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.insertDataset. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
GET /projects/{projectId}/datasets/{datasetId}/tables
List tables
| Detail | Value |
|---|---|
| Operation ID | database.listTables |
| Method | GET |
| Path | /projects/{projectId}/datasets/{datasetId}/tables |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.listTables. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
POST /projects/{projectId}/queries
Run a SQL query
| Detail | Value |
|---|---|
| Operation ID | database.queryJob |
| Method | POST |
| Path | /projects/{projectId}/queries |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.queryJob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
GET /projects/{projectId}/jobs
List jobs
| Detail | Value |
|---|---|
| Operation ID | database.listJobs |
| Method | GET |
| Path | /projects/{projectId}/jobs |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.listJobs. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
GET /projects/{projectId}/jobs/{jobId}
Get job details
| Detail | Value |
|---|---|
| Operation ID | database.getJob |
| Method | GET |
| Path | /projects/{projectId}/jobs/{jobId} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.getJob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
POST /projects/{projectId}/jobs/{jobId}/cancel
Cancel a job
| Detail | Value |
|---|---|
| Operation ID | database.cancelJob |
| Method | POST |
| Path | /projects/{projectId}/jobs/{jobId}/cancel |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.cancelJob. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.
GET /projects/{projectId}/datasets/{datasetId}/tables/{tableId}/data
List table data
| Detail | Value |
|---|---|
| Operation ID | database.listTableData |
| Method | GET |
| Path | /projects/{projectId}/datasets/{datasetId}/tables/{tableId}/data |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google BigQuery connection from the Connection dropdown.
- In the Operation dropdown, select
database.listTableData. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google BigQuery API reference.