Google BigQuery
Google BigQuery SQL query and dataset
Google BigQuery is the serverless data warehouse — petabyte-scale SQL on demand, billed per-query bytes scanned, used by data teams across Google-friendly stacks. Tiny Command exposes three actions, no triggers (BigQuery doesn't emit query/table-change webhooks directly; for event-driven workflows, use Cloud Logging sinks or Eventarc to dispatch via Pub/Sub to a Tiny Command webhook trigger URL): Run Query (execute a SQL query, returns the resulting rows; Standard SQL by default, Legacy SQL via parameter), List Datasets (every dataset in the project — datasets are BigQuery's "folder" for tables), List Tables (within a dataset, with metadata about schema and size). The connection uses a Google Cloud service-account key (JSON) with bigquery.jobs.create plus bigquery.tables.getData on the target resources. Run Query is the workhorse — a scheduled Tiny Command workflow fires Run Query nightly to compute the previous day's KPIs, then fans the results out to Notion, Slack, or a dashboard email. Query cost is per bytes scanned; tight WHERE clauses and partition pruning save real money.
Do anything Google BigQuery can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| List Datasets | 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. |
| 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. |
| 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. |
Pre-built Google BigQuery workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Google BigQuery event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Google BigQuery into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Google BigQuery once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Google BigQuery field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Google BigQuery integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Google BigQuery to Tiny Command?
What Google BigQuery triggers does Tiny Command support?
What Google BigQuery actions can I run from a workflow?
Is the Google BigQuery integration real-time?
Do I need to write code to use Google BigQuery with Tiny Command?
How much does the Google BigQuery integration cost?
More other apps people connect.
Same category as Google BigQuery, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google BigQuery.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
