NewJobs: scheduled actions created from chat, personal or shared.Learn more

BigQuery + Memtro

Read-only GoogleSQL over your BigQuery warehouse, with a dry run before every expensive scan.

Give Memtro a service account with viewer roles and the model can browse datasets, read table schemas and run SELECT queries. It dry-runs first when a scan could be large, so you see bytes processed before you pay for them.

What you can do with BigQuery in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right BigQuery tool, reads what it needs, and answers with the source cited.

01

Warehouse questions

Ask how many orders a customer placed last quarter and Memtro writes the GoogleSQL, runs it and cites the table.

02

Cost before the scan

It dry-runs first when a query could be large, so you see the bytes scanned before paying for them.

  • List datasets, tables and columns, including nested RECORD fields
  • Run one SELECT or WITH query at a time, rows capped, 20 second timeout
  • Dry-run any query to see the bytes it would scan
  • Tokens use the bigquery.readonly scope, so nothing can be written

Ask it like this

Questions people ask once BigQuery is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›How many orders did Acme place last quarter, from the warehouse?
  • ›Which tables in the analytics dataset hold customer emails?
  • ›How much would it cost to scan events for the last 30 days?

Where it fits

Teams that get the most from BigQuery in Memtro, with the rest of their stack attached.

Better together

A record in BigQuery is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in Databases and warehouses

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01Create a service account in Google Cloud and grant it BigQuery Data Viewer and BigQuery Job User
  2. 02Add a JSON key and download it
  3. 03Paste the key file on Dashboard → Connections → BigQuery, set the location (US, EU, a region) and name it
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The BigQuery tools are the same everywhere.

Clients and agents →

Questions

Can Memtro change anything in BigQuery?
No. The BigQuery connector is read-only: every tool reads, searches or lists. Nothing is created, sent, updated or deleted, and the credentials you give it should be read-only too.
Who can use a BigQuery connection?
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my BigQuery data?
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect BigQuery?
Service account key. Create a service account in Google Cloud and grant it BigQuery Data Viewer and BigQuery Job User.

Connect BigQuery in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.