> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/tables/exporting-tables/google-bigquery.md).

# Google BigQuery

The table export modal **Integrations** tab allows export of Redivis tables to [Google BigQuery](https://cloud.google.com/bigquery).

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FWIiuooo0sCKXGizE6ULh%2Fredivis.com_datasets_7br5-41440fjzk_tables_6fff-7hqb797cb_exportTable%3D6fff-7hqb797cb%20(1).png?alt=media&amp;token=989d01bc-beac-46cd-aaf1-d9ea3137c81e" alt=""></div>

To export data to BigQuery, select **Export**, then fill out the subsequent modal.

You'll need to authenticate a Google account, and then specify the *BigQuery project*, *BigQuery dataset*, and *BigQuery table*.

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FNueqUBqmVsGzWTWtwxYh%2Fredivis.com_datasets_7br5-41440fjzk_tables_6fff-7hqb797cb_exportTable%3D6fff-7hqb797cb%26exportDestination%3Dintegration%20(1).png?alt=media&amp;token=7f0d159a-20ad-475c-8574-aec5a5ca6042" alt=""></div>

Once you confirm the export, your data will begin transferring to the specified BigQuery location and will provide a live-updating status of the transfer.

### Exporting to BigQuery table in a VPC

If the Google Cloud project containing your desired BigQuery table is associated with a [Virtual Private Cloud](https://cloud.google.com/vpc) (VPC), you will need to configure an **ingress policy** on your Google Cloud organization to allow data export from Redivis to that table.

**Configure on Google Cloud Console**

To configure your VPC to allow Redivis to export to BigQuery:

1. Go to your Google Cloud Console's [VPC Service Controls dashboard](https://console.cloud.google.com/security/service-perimeter) and select your VPC
   1. Select your Google *organization* in the top-left project picker (rather than a specific project) to list your organization's VPCs. You'll need a VPC Service Controls admin role to make changes.
2. Select the perimeter that contains the desired bucket's project to see the Service perimeter details&#x20;

   1. If **BigQuery API** is listed under **Restricted Services**, you *will* need to configure an ingress policy to write to the bucket.
   2. Confirm the BigQuery table's project is listed under **Projects.**

   <figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FykclffhaWj6vbeTtoe6g%2FCleanShot%202026-10-05%20at%2015.00.16%402x.png?alt=media&amp;token=1bd82272-a4aa-4361-a136-ce14b43b3ad6" alt=""><figcaption></figcaption></figure>
3. Select **Edit,** then under **Ingress policy**, select **Add an ingress rule**, and configure the following options:
   1. From, identities: Add `user:name@university.edu` to allow just your Redivis user to export, or `ANY_USER_ACCOUNT` to allow anyone to export from Redivis.
   2. From, sources: Add the following Google Cloud project: `som-phs-redivis-prod`. This project is managed by Redivis, and ensure that exports from *only* the Redivis platform can land in your bucket.
   3. To, resources: Add your BigQuery table's Google Cloud project.
   4. To, operations or IAM roles: Add the `bigquery.googleapis.com` to allow writes to your BigQuery table.
4. **Save** the policy, and then export any Redivis table to your BigQuery table, per the [instructions above](/reference/tables/exporting-tables/google-cloud-storage.md).

**Configure with `gcloud` CLI tool**

To do the above configuration using the `gcloud` CLI tool, you can use the following shell script, using the YAML file below. You'll need the VPC name and access policy ID to modify it, as well as the Google Cloud project number.

{% hint style="info" %}
If your VPC has existing ingress policies, you should use `perimeters describe` (or `dry-run describe`) to get the existing YAML configuration, and merge it with the file below.
{% endhint %}

```bash
# Dry-run config (recommended first)
gcloud access-context-manager perimeters dry-run update PERIMETER_NAME \
  --set-ingress-policies=ingress.yaml \
  --policy=POLICY_ID

# Enforced config, once validated
gcloud access-context-manager perimeters update PERIMETER_NAME \
  --set-ingress-policies=ingress.yaml \
  --policy=POLICY_ID
```

Use the following `ingress.yaml` file, which contains ingress rule described above.

```yaml
# ingress.yaml
- ingressFrom:
    identities:
      - user:name@university.edu
    sources:
      - resource: projects/936051303296
  ingressTo:
    resources:
      - projects/DESTINATION_PROJECT_NUMBER
    operations:
      - serviceName: bigquery.googleapis.com
        methodSelectors:
          - method: '*'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.redivis.com/reference/tables/exporting-tables/google-bigquery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.