Skip to content

Google BigQuery, without opening Google BigQuery.

What is in the warehouse, and what the last job did.

  • Free to start
  • No card
  • Reads only, nothing to approve
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Google BigQuery details, and Ray takes it from there.

  • @Ray what tables are in the events dataset?

  • @Ray what does the schema of the orders table look like?

  • @Ray did last night's load job finish, and how long did it take?

  • @Ray show me the last ten rows that landed in the events table.

What Ray can and cannot do in Google BigQuery

Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.

13 reads wired, and nothing that writes.

Runs on its own

What Ray reads in Google BigQuery

  • Datasets, tables, and their schemas
  • Jobs, models, and routines
  • Table data and query results

Reading changes nothing, so Ray never stops to ask whether it may look something up.

No send, no spend

What Ray answers with

Ray reads Google BigQuery and answers from it in the thread. Writing to Google BigQuery is not switched on yet, so there is nothing here to approve.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Create or delete a dataset, table, or model
  • Change a dataset or table schema
  • Cancel a job

How Ray works with Google BigQuery

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect Google BigQuery

    One click, right where you asked. Ray posts a connect card, you authorise Google BigQuery with your own account, and the work you asked for picks up where it left off.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    Ray answers where you asked

    Ray only reads Google BigQuery, so there is nothing here to approve. It looks up what it needs and replies in the thread.

and the rest

Priya

@Ray the checkout bug is back. Take a look in Google BigQuery, and tell Dana it is being looked at.

Ray

Checked Google BigQuery. The spec was last edited on Tuesday and the open question about refunds is still unanswered.

Works with your stack

Ray uses Google BigQuery together with the rest of your tools.

One ask can read Google BigQuery, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting Google BigQuery to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Google BigQuery and it can do the Google BigQuery part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Every person on the team connects their own Google BigQuery account, so Ray can only reach what that person can already reach, and the history in Google BigQuery shows who actually asked.

Security and permissions

  • You authorise Google BigQuery on its own login screen. Your password never passes through Ray.
  • Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • Disconnect Google BigQuery in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Google BigQuery and Ray, answered

The questions teams ask before they connect Google BigQuery. Every answer is how this integration is built rather than a promise about it.

More analytics & bi integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Google BigQuery.

Free to start, no credit card, and it asks before it acts.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.