ActionGoogle BigQueryUpdated September 2026

What BigQuery datasets are in this project?

Short answer: You can list datasets in Google BigQuery by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google BigQuery List Datasets action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Datasets in Google BigQuery — start free All 3 Google BigQuery actions

List Datasets in Google BigQuery — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Project ID project_id	string	Required	my-gcp-project-12345
Max Results max_results	number	Optional	–

Sample request

{
  "project_id": "my-gcp-project-12345",
  "max_results": "{{trigger.max_results}}"
}

Returns

{
  "datasets": [
    {
      "location": "US",
      "datasetReference": {
        "datasetId": "analytics_prod",
        "projectId": "my-project"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Datasets.

Any of these apps can fire this action as part of a workflow.

Gmail → Google BigQuery

1 Gmail triggers

Slack → Google BigQuery

13 Slack triggers

Google Sheets → Google BigQuery

2 Google Sheets triggers

HubSpot → Google BigQuery

18 HubSpot triggers

FAQ

Questions about List Datasets.

What does the List Datasets action do in Google BigQuery?

Returns every dataset in the connected GCP project with name, location, default retention. Useful for resolving dataset names in workflow setup and for inventorying the project's data warehouse structure.

What inputs does List Datasets require?

Required: Project ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Google BigQuery returns an error?

The run history shows the failed step with its input and the error message Google BigQuery returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Datasets support batch operations?

Run List Datasets inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Google BigQuery's rate limits.

More actions

Other Google BigQuery actions.

Action

List Tables in Dataset

Returns the tables, views, and external tables in a dataset with size and row counts. Useful for query-construction workflows that need to validate table existence before running a query.

Action

Run BigQuery SQL Query

Executes a Standard SQL query and returns the resulting rows. Cost scales with bytes scanned, so tight WHERE clauses on partitioned columns save real money. Use dry_run=true to preview cost before running large queries.

List Datasets in Google BigQuery — start free