← All integrations

Google BigQuery

62 operations0 webhooks

Serverless data warehouse for running SQL analytics on massive datasets at scale.

Supported operations

  • Create Data ExchangeWrite

    Create a new data exchange

  • Create ListingWrite

    Create a new listing (shareable dataset) in a data exchange

  • Create Query TemplateWrite

    Create a new query template in a data exchange

  • List Dataexchanges ListingsRead-only

    List data exchanges in a location

  • List ListingsRead-only

    List listings in a data exchange

  • List Organization Data ExchangesRead-only

    List data exchanges across an organization

  • List Query TemplatesRead-only

    List query templates in a data exchange

FAQ

Install corsair and @corsair-dev/googlebigquery, add the Google BigQuery plugin, and connect with OAuth. Then call methods like corsair.googlebigquery.api.analyticsHub.createDataExchange() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. Google BigQuery needs an OAuth app with scopes that match what you automate. Register the app in Google BigQuery, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Google BigQuery, GitHub, Notion, Stripe, and the rest. Trigger Google BigQuery from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for serverless data warehouse for running sql analytics on massive datasets at scale. Common builds include sync jobs, admin tooling, and agents that call Google BigQuery APIs from your backend. Local DB entities let you query synced Google BigQuery records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Google BigQuery API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/googlebigquery in the open repo. When Google BigQuery ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Google BigQuery data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Google BigQuery data on your behalf.