List Datasets
bigquery.list_datasets
ActionDatabases & warehousesconnection required
Calls the BigQuery API GET projects/{project}/datasets.
List the BigQuery datasets in a GCP project.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google BigQuery
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
max_results Max datasets (1-1000). | number | No | 100 | ≥ 1 | — |
page_token next_page_token from a previous run, to fetch the next page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
datasets | array | — |
count | number | — |
next_page_token Set only when another page exists; feed it back as page_token. | string | — |
{
"count": 0,
"datasets": [],
"next_page_token": ""
}See List Datasets run in a workflow.
In a technical demo we add the Google BigQuery connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.