Skip to content
Google BigQuery logo

Google BigQuery integration

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

Actions
10
Triggers
4
Auth
OAuth 2.0 or Custom auth
License
MIT, open source
Updated
September 2026

About the Google BigQuery integration

Add the Google BigQuery piece to a flow, connect your account once, and the rest of the builder can read from it and write to it. Because the piece is open source you can run it on our cloud or self-host it, and combine Google BigQuery with 760+ other apps in the same flow.

Triggers

Start a flow the moment something happens in Google BigQuery

Each trigger below can start a flow on its own, either instantly or on a schedule.

  • New Row

    Triggers when a new row is added to a BigQuery table. Polls every 5 minutes by comparing the latest value in a sort column against the previous check.

    5 fields

  • Updated Row

    Triggers when an existing row is updated in a BigQuery table. Requires an `updated_at` TIMESTAMP column that is set whenever a row changes.

    6 fields

  • Query Job Completed (With Row Data)

    Triggers when a BigQuery query job finishes successfully. Each flow run receives the job metadata and the result rows from that query.

    2 fields

  • New Job Completed

    Triggers when any BigQuery job (query, load, copy, or extract) finishes. Returns the job metadata including status, type, and timing.

    2 fields

Actions

Everything Activepieces can do in Google BigQuery

Drop any of these into a flow and fill in the fields. No code is required.

  • Run a Query

    Execute a SQL query on BigQuery and return the results as flat rows

    5 fields

  • Create Row

    Creates a single new row in a BigQuery table. Column fields are loaded from the table schema.

    4 fields

  • Create Rows

    Creates new rows of data in a BigQuery table (accepts an array of row objects). Rows are available to query within seconds.

    6 fields

  • Delete Rows

    Deletes one or more rows from a BigQuery table using a SQL WHERE condition.

    5 fields

  • Update Row(s)

    Updates one or more existing rows in a BigQuery table using SQL SET and WHERE expressions.

    6 fields

  • Find One Row

    Find a single row by specifying a WHERE clause and an optional ORDER BY. Returns the first matching row, or empty if none found.

    6 fields

  • Find or Create Record

    Searches for a row matching a WHERE clause. If found, returns it. If not found, inserts the provided row data and returns that.

    6 fields

  • Get Rows for Job Completed

    Retrieves the result rows from a completed BigQuery query job by Job ID. Use this after a "Query Job Completed" trigger to fetch the full result set.

    4 fields

  • Import Data

    Imports a batch of rows into a BigQuery table. Accepts a JSON array or newline-delimited JSON (NDJSON). Large datasets are automatically split into chunks.

    6 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Use Google BigQuery in a flow

Connect Google BigQuery once and every trigger and action above is yours to drop into the builder, alongside 760+ other apps. Free to start, on our cloud or your own servers.

Google BigQuery, answered.

Yes. Activepieces is open source and free to start, and the Google BigQuery piece is included on every plan, from the free cloud tier to any self-hosted deployment.

Add the Google BigQuery piece to a flow, then authenticate with OAuth 2.0 or Custom auth. Once connected, its 4 triggers and 10 actions are available anywhere in the builder.

"New Row" can start a flow that runs "Run a Query", and you can chain Google BigQuery together with any of 760+ other apps and AI steps in between.

Yes. Activepieces is fully self-hostable, so you can run the Google BigQuery piece on your own infrastructure with your connections and your data staying in your environment.

Yes. Every piece you connect can be exposed over one Activepieces MCP server, so Claude, Cursor, Windsurf or any MCP client can call Google BigQuery actions as tools.