Google BigQuery

Overview

Connect Google BigQuery with Flows360

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

Use the Google BigQuery connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 10 actions and 4 triggers.

Available actions

• Run a Query
• Create Row
• Create Rows
• Delete Rows
• Update Row(s)
• Find One Row
• Find or Create Record
• Get Rows for Job Completed
• Plus 2 additional declared actions.

Available triggers

• New Row
• Updated Row
• Query Job Completed (With Row Data)
• New Job Completed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: Google BigQuery
• Package: @activepieces/piece-google-bigquery@0.1.0
• Exact artifact digest: sha256:482358ac997c6eeccac80d85a2270288fcb6df2be88d057b2e66635e0c0b24db
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

OAUTH2, CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Run a Query (run_query), Execute a SQL query on BigQuery and return the results as flat rows Classification: read.
• Create Row (create_row), Creates a single new row in a BigQuery table. Column fields are loaded from the table schema. Classification: read.
• Create Rows (create_rows), Creates new rows of data in a BigQuery table (accepts an array of row objects). Rows are available to query within seconds. Classification: read.
• Delete Rows (delete_rows), Deletes one or more rows from a BigQuery table using a SQL WHERE condition. Classification: read.
• Update Row(s) (update_rows), Updates one or more existing rows in a BigQuery table using SQL SET and WHERE expressions. Classification: read.
• Find One Row (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. Classification: read.
• Find or Create Record (find_or_create_row), Searches for a row matching a WHERE clause. If found, returns it. If not found, inserts the provided row data and returns that. Classification: read.
• Get Rows for Job Completed (get_rows_for_job), 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. Classification: read.
• Import Data (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. Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• New Row, polling.
• Updated Row, polling.
• Query Job Completed (With Row Data), polling.
• New Job Completed, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

Authentication profiles

Triggers

Setup

Setup

1. Add the Google BigQuery connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• Markdown (instructions), optional.
• Service Account JSON (serviceAccountJson), required.

OAuth scopes

• https://www.googleapis.com/auth/bigquery
• email

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-google-bigquery@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 10 actions and 4 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Related documentation