Skip to content
Analytics & Data

Connect Google BigQuery to Sortment

Connect Google BigQuery to Sortment so its AI agents can use 63 Google BigQuery actions in your lifecycle programs, from audiences and campaigns to reporting.

Actions
63
Triggers
—
Authentication
OAuth2, Google Service Account
Category
Analytics & Data

What Sortment's agents can do in Google BigQuery

36 of 63 actions shown.

  • Cancel BigQuery Job
  • Create Capacity Commitment
  • Create BigQuery Connection
  • Create Analytics Hub Data Exchange
  • Create Analytics Hub Listing
  • Create BigQuery Dataset
  • Create Analytics Hub Listing
  • Create BigQuery Data Policy (v2beta1)
  • Create Analytics Hub Query Template
  • Create BigQuery Reservation
  • Create BigQuery Reservation Assignment
  • Create BigQuery Routine
  • Create BigQuery Table
  • Delete BigQuery Dataset
  • Delete BigQuery Job Metadata
  • Delete BigQuery ML Model
  • Delete BigQuery Routine
  • Delete BigQuery Table
  • Get BigQuery ML Model
  • Get BigQuery Connection IAM Policy
  • Get BigQuery Dataset Metadata
  • Get BigQuery Job
  • Get BigQuery Query Results
  • Get BigQuery Routine
  • Get BigQuery Routine IAM Policy
  • Get BigQuery Service Account
  • Get BigQuery Table IAM Policy
  • Get BigQuery Table Schema
  • Insert Data into BigQuery Table
  • Insert BigQuery Job
  • Insert BigQuery Job with Upload
  • List Analytics Hub Listings
  • List BigQuery Connections
  • List BigQuery Capacity Commitments
  • List Data Exchange Listings
  • List BigQuery Datasets

How it works

  1. 1

    Connect

    Connect it in Settings › Connectors. Most tools take one click to authorise.

  2. 2

    Put agents to work

    Strategy, Content and Analyst AI can read from it and act in it as part of your lifecycle programs.

  3. 3

    Approve and measure

    You review every change before it goes live, and Sortment measures the lift.

See Sortment work with Google BigQuery.

Book a 30-minute call. We'll walk you through Sortment with your goals, your data and your stack in mind.

No migration · Works alongside your existing stack