Google BigQuery integration

Quick start

Call Google BigQuery from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Google BigQuery's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "GOOGLEBIGQUERY_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for Google BigQuery. End-users click Connect on the integration card in your app, complete the OAuth flow with Google BigQuery, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2, GOOGLE_SERVICE_ACCOUNT.

Available actions

63 actions exposed via the Google BigQuery integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• GOOGLEBIGQUERY_CANCEL_JOB
• GOOGLEBIGQUERY_CREATE_CAPACITY_COMMITMENT
• GOOGLEBIGQUERY_CREATE_CONNECTION
• GOOGLEBIGQUERY_CREATE_DATA_EXCHANGE
• GOOGLEBIGQUERY_CREATE_DATAEXCHANGES_LISTINGS
• GOOGLEBIGQUERY_CREATE_DATASET
• GOOGLEBIGQUERY_CREATE_LISTING
• GOOGLEBIGQUERY_CREATE_LOCATIONS_DATAPOLICIES
• GOOGLEBIGQUERY_CREATE_QUERY_TEMPLATE
• GOOGLEBIGQUERY_CREATE_RESERVATION
• GOOGLEBIGQUERY_CREATE_RESERVATION_ASSIGNMENT
• GOOGLEBIGQUERY_CREATE_ROUTINE