01
Ask the warehouse in a sentence
A lead asks for last quarter’s refund rate by region — Copilot writes the query, runs it and answers, showing the SQL it used.
Integrations · Analytics & data
Google BigQuery in the conversation.
Google’s warehouse, and often the only place where every system’s data meets. Connect it once and your copilot works with datasets, tables, views and query results without leaving the thread — and your workflows can act on it while the customer is still typing.
No credit card required · 7-day free trial
Google BigQuery
Analytics & data
01 · COPILOT
Ask for it in plain language. It does the Google BigQuery part.
Copilot rides inside the inbox. With Google BigQuery connected it reads datasets, tables, views and query results and acts on them from the same panel as the conversation — no second tab, no copying an order number across.
- Run a query and read the results
- List datasets and tables
- Read a table’s schema before querying it
What a specific connection exposes is decided by Google BigQuery, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
02 · WORKFLOWS
Read Google BigQuery from inside a workflow.
Google BigQuery is a place a workflow looks things up rather than one that starts it. Trigger on a conversation, a schedule or another app's event, then use an AI Agent step to work in Google BigQuery and hand the answer to the steps that follow — a message, a CRM update, an escalation.
If Google BigQuery does publish events to your workspace, they appear in the trigger picker the moment the connection is made.
03 · THE AI AGENT STEP
One step that decides which Google BigQuery tools to call.
A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.
You declare the output
The rows you name become the variables downstream steps read, so a branch can test what Google BigQuery said.
You cap the effort
A step budget and a model tier per node — the loop stops where you told it to.
Only what you switched on
The loop can call the Google BigQuery tools you left enabled and nothing else.
What teams do with it
Two ways Google BigQuery earns its connection.
02
Reports that arrive as messages
A scheduled workflow queries BigQuery and posts the number to the channel that cares, instead of a dashboard nobody opens.
Setup
Connect Google BigQuery in about a minute.
- 1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
- 2
Find Google BigQuery in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Google BigQuery from its card.
- 3
Authorize with your own Google BigQuery account
You sign in on Google BigQuery's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
- 4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.
Google BigQuery questions.
How do I connect Google BigQuery to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Google BigQuery. Connecting it opens Google BigQuery's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Google BigQuery?
Work of this kind: run a query and read the results; list datasets and tables; read a table’s schema before querying it. The exact list depends on what your Google BigQuery account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Google BigQuery tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Google BigQuery connection is a matter of leaving the writes off.
Can a workflow use Google BigQuery without a trigger from it?
Yes. Google BigQuery is read from inside a workflow rather than starting one: a workflow triggered by a conversation, a schedule or another app's event uses an AI Agent step to work in Google BigQuery and hand its answer to the steps that follow.
Who in my team can connect Google BigQuery?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Google BigQuery account that authorized it, so a analytics & data connection is only ever as broad as the account behind it.
More analytics & data
Rarely just one app.
Google AnalyticsWeb analytics, and the number most teams argue about on a Monday.
SupabaseA Postgres platform with auth and storage, and the application database for a lot of modern products.Clarity AI MCPSimulate SFDR 2.0 fund classifications from name, ISIN, or CUSIP using Clarity AI's disclosure data and modeling.
DubShort link management platform with analytics and API for creating, managing, and tracking branded short links.ExistExist is a personal analytics app that combines data from various services to help users understand and improve their lives.GongGong is a platform for video meetings, call recording, and team collaboration.See it on your own inbox
Try the whole thing, today.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.