Search and data
Google BigQuery for AI agents.
Managed auth, ready-made tools.
Explore datasets and tables, run SQL queries and insert rows in Google BigQuery on behalf of each of your users.
About Google BigQuery
With the Google BigQuery connector, your agent works with each user’s own Google Cloud projects. It can list datasets and tables, read a table’s schema, run a SQL query, create a dataset or table and insert rows, using only the tools your project allows.
Google BigQuery is Google Cloud’s serverless data warehouse for analyzing large datasets with SQL.
Tools
What your agent can do in Google BigQuery.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google BigQuery connection.
-
List datasets
Readgoogle_bigquery_list_datasetsList the datasets in a project.
-
List tables
Readgoogle_bigquery_list_tablesList the tables in a dataset.
-
Get a table
Readgoogle_bigquery_get_tableRead a table's schema and details.
-
Run a query
Readgoogle_bigquery_run_queryRun a SQL query and get the results.
-
Create a dataset
Writegoogle_bigquery_create_datasetCreate a new dataset.
-
Create a table
Writegoogle_bigquery_create_tableCreate a table with a schema.
-
Insert rows
Writegoogle_bigquery_insert_rowsStream new rows into a table.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Google BigQuery, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent explore tables and run queries, and switch off
google_bigquery_insert_rowsso it can never write data. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading datasets but not inserting rows. A call outside them is refused.
Get started
Connect Google BigQuery
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google BigQuery
Each end user authorizes their own Google BigQuery account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google BigQuery account, once. const connection = await agent200 .user("user_123") .connect("google_bigquery"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google BigQuery tools
Name the user, the model and the tools. The model decides which Google BigQuery tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "What tables are in the analytics dataset", tools: ["google_bigquery"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Google's own sign-in page. You never see or store their Google password.
-
What access is requested
The scopes the connection needs, such as viewing BigQuery data or managing BigQuery data, listed on Google's authorization screen. Users can remove the app later from their Google account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google BigQuery connector and how to use it.
Connector: Google BigQuery, through Agent200. In code: "google_bigquery". What it does: Explore datasets and tables, run SQL queries and insert rows in Google BigQuery on behalf of each of your users. Page: https://www.agent200.com/connectors/google-bigquery/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google BigQuery's own page, through the authorization link Agent200 returns. Never ask a user for a Google BigQuery password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_bigquery_list_datasets, google_bigquery_list_tables, google_bigquery_get_table, google_bigquery_run_query. Write tools: google_bigquery_create_dataset, google_bigquery_create_table, google_bigquery_insert_rows. Name "google_bigquery" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/google-bigquery/framework/claude/ https://www.agent200.com/connectors/google-bigquery/framework/chatgpt/ https://www.agent200.com/connectors/google-bigquery/framework/claude-code/ https://www.agent200.com/connectors/google-bigquery/framework/muse/ https://www.agent200.com/connectors/google-bigquery/framework/grok-bot/ https://www.agent200.com/connectors/google-bigquery/framework/openai-dots/ https://www.agent200.com/connectors/google-bigquery/framework/claude-duet/ https://www.agent200.com/connectors/google-bigquery/framework/hermes-agent/ https://www.agent200.com/connectors/google-bigquery/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/google-bigquery.md
Guides
Use Google BigQuery with the AI you build on.
Step-by-step setup for Google BigQuery with a specific model, assistant or agent framework.
-
Google BigQuery + Claude
How to connect Google BigQuery to Claude
-
Google BigQuery + ChatGPT
How to connect Google BigQuery to ChatGPT
-
Google BigQuery + Claude Code
How to connect Google BigQuery to Claude Code
-
Google BigQuery + Muse
How to connect Google BigQuery to Muse
-
Google BigQuery + Grok Bot
How to connect Google BigQuery to Grok Bot
-
Google BigQuery + OpenAI Dots
How to connect Google BigQuery to OpenAI Dots
-
Google BigQuery + Claude Duet
How to connect Google BigQuery to Claude Duet
-
Google BigQuery + Hermes Agent
How to connect Google BigQuery to Hermes Agent
-
Google BigQuery + OpenClaw
How to connect Google BigQuery to OpenClaw
FAQ
Google BigQuery and Agent200, answered.
Who handles the Google BigQuery OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google BigQuery.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google BigQuery connection, never another user's. It cannot reach anything the user or Google BigQuery has not authorized.
Can I limit what my agent can do in Google BigQuery?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.