List Datasets: Google BigQuery action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Datasets support batch operations?

Yes. Run List Datasets inside a Loop node to process arrays. Tiny Command handles Google BigQuery's rate limits automatically so you don't have to throttle manually.

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.

What BigQuery datasets are in this project?

The fields this action accepts.

Apps that pair well as the trigger for List Datasets.

Questions about List Datasets.

Other Google BigQuery actions.

Send list datasets from your workflows.