How does the BigQuery Integration work?

This article explains the warehouse import and warehouse export settings used by Pylon's BigQuery integration. You can install the integration from the BigQuery page.

Unlike Snowflake, BigQuery doesn't have user-managed warehouses or roles — compute is handled automatically by Google, and access is controlled through service accounts and IAM roles in Google Cloud. You'll authenticate Pylon by uploading a service account JSON key. See 📄 How do I create a BigQuery service account key for an import sync? for step-by-step instructions on creating the key

Warehouse Export

Warehouse exports require the following information:

Project ID

The Google Cloud project that data will be written to. We recommend using a dedicated project for Pylon data, or at minimum a dedicated dataset within an existing project.

Dataset

The BigQuery dataset that data will be written to. We recommend creating a new dataset for Pylon data. This is the BigQuery equivalent of a Snowflake schema.

Table

The name of the table that data will be written to. Pylon will automatically create this table for you with the proper schema.

Location (Optional)

The regional or multi-regional location of your dataset (e.g. US, EU, us-east1). If not specified, Pylon defaults to the US multi-region. The location must match the location of the dataset you're writing to.

Service Account Key

A JSON key for a service account that has write access to the destination dataset. The service account needs:

- BigQuery Data Editor (roles/bigquery.dataEditor) on the destination dataset — so Pylon can create the table and insert rows.

- BigQuery Job User (roles/bigquery.jobUser) on the project — so Pylon can run load jobs.

Warehouse Import

Warehouse imports require the following information:

Project ID

The Google Cloud project that contains the data you want to sync. This is the project the service account will run queries in.

Service Account Key

A JSON key for a service account that has read access to the data you want to sync. You will only be able to see and sync datasets and tables that this service account has permission to view. We recommend making sure the service account is read-only. The service account needs:

• BigQuery Data Viewer (roles/bigquery.dataViewer) — granted either on the project, or scoped to specific datasets if you want to limit what Pylon can see.

• BigQuery Job User (roles/bigquery.jobUser) on the project — so Pylon can execute the sync query.

Location (Optional)

The regional or multi-regional location of the dataset you're syncing from. If your data lives outside the US multi-region, set this so queries run in the correct location.

You will select the dataset, table, and columns you want to sync during the sync creation flow.

You can either choose from existing tables or write SQL directly — the columns of the resulting table can be mapped directly into fields on accounts or contacts.