Short answer: Drop the "Google BigQuery → List Tables in Dataset" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"project_id": "{{trigger.project_id}}","dataset_id": "analytics_prod","max_results": "{{trigger.max_results}}"}
{"tables": [{"type": "TABLE","tableReference": {"tableId": "events","datasetId": "analytics_prod","projectId": "my-project"}}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.