ActionGoogle BigQueryUpdated May 2026

What tables are in this BigQuery dataset?

Short answer: Drop the "Google BigQuery → List Tables in Dataset" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Google BigQuery actions

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	—
Dataset ID dataset_id	string	Required	The Dataset ID assigned by Bigquery. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Max Results max_results	number	Optional	—

Sample request

{
  "project_id": "{{trigger.project_id}}",
  "dataset_id": "analytics_prod",
  "max_results": "{{trigger.max_results}}"
}

Returns

{
  "tables": [
    {
      "type": "TABLE",
      "tableReference": {
        "tableId": "events",
        "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 Tables in Dataset.

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 Tables in Dataset.

What does the List Tables in Dataset action do in Google BigQuery?

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.

What inputs does List Tables in Dataset require?

Required: Project ID, Dataset 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 Tables in Dataset support batch operations?

Yes. Run List Tables in Dataset 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