Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Business intelligence ]

Google BigQuery integration for your workflows.

Connect Google BigQuery to Collabase once and use 10 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inOAuth 2.0
CategoryBusiness intelligence
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Google BigQuery in Collabase

Connect Google BigQuery to Collabase once and use 10 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Query, analyze, and stream data into Google BigQuery — the fully managed, serverless data warehouse

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Google BigQuery and connect your account.
  3. Add a trigger or an action to the workflow.

[ Business intelligence ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Google BigQuery

What can I automate with Google BigQuery in Collabase?

Google BigQuery brings 10 actions and 4 triggers, for example Run a Query, Create Row, Create Rows, Delete Rows and 6 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Google BigQuery to Collabase?

You open the integrations in the workspace settings, choose Google BigQuery and connect your account once, using OAuth 2.0. After that all triggers and actions are available in the workflow.

Can Google BigQuery start a workflow?

Yes. Google BigQuery provides 4 triggers, for example New Row, Updated Row, Query Job Completed (With Row Data) and 1 more. The workflow runs as soon as the event happens.

Does the Google BigQuery integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.