Integrations / Google BigQuery

Google BigQuery

Google's serverless data warehouse

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A GCP project with BigQuery datasets Telara should query.

Permission to create a service account and grant it BigQuery Job User plus Data Viewer on those datasets. Project Owner is more than Telara needs.

Vendor setup

Get the credential

Create a service account

In Google Cloud Console, IAM & Admin → Service Accounts → Create service account. Name it for Telara.

Grant dataset access

Grant the service account BigQuery Job User at the project, and BigQuery Data Viewer on each dataset Telara should see (dataset → Sharing → Permissions).

Download the JSON key

Open the service account → Keys → Add key → Create new key → JSON. The file downloads once.

Paste in Telara

Settings → Integrations → Google BigQuery. Paste the JSON and the project id. User OAuth is a fallback, not the default.

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Project Id

Service account

Service account authentication with JSON credentials

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for

Service Account Json
Project Id

Knowledge

What gets indexed

Resource	Coverage
Dataset	Partial — not every record the vendor holds is synced
Table	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Dataset	Up to 1 day	Removed records disappear on the next full sync
Table	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Dataset, Table.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

A key from a different project will connect then see nothing.

This is not the GCP cloud connector. Billing and resource inventory live on that page.