> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-sources/bigquery.md).

# BigQuery

Connect Google BigQuery to Felt with a service account JSON key to map tables, views, or SQL query results.

{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

Connect [Google BigQuery](https://cloud.google.com/bigquery) with a service account to add tables and views to maps or query them with [SQL](/upload-anything/sql-queries.md). Felt reads from BigQuery without writing data back.

{% embed url="<https://youtu.be/3SvQtLHcyxA?si=OBX_mqWLK4RFmc70>" %}

## Connect BigQuery

[Create a service account](#create-a-service-account) for Felt. Then follow the steps in [Add a source](/upload-anything/data-sources/add-a-source.md#connect-a-source) and select **BigQuery**.

In **Connection**, fill in these fields.

| Field                | Required | What to enter                                                                                                                                                                     |
| -------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project ID           | Yes      | The ID of your Google Cloud project, such as `my-company-project`.                                                                                                                |
| Dataset              | No       | One BigQuery [dataset](https://cloud.google.com/bigquery/docs/datasets-intro#datasets), the container that holds your tables. Leave it empty to read all datasets in the project. |
| Service Account JSON | Yes      | The JSON key file for the service account you created for Felt.                                                                                                                   |

## Create a service account

1. In the Google Cloud console, open [**IAM & Admin** > **Service accounts**](https://console.cloud.google.com/iam-admin/serviceaccounts) and create a service account for Felt.
2. Grant it these roles on your project: **BigQuery Data Viewer**, **BigQuery Metadata Viewer**, and **BigQuery Job User**.
3. In the service account's **Keys** tab, add a key of type JSON. The key file downloads.
4. In Felt, upload the key file to **Service Account JSON**.

For [external tables](https://cloud.google.com/bigquery/docs/external-tables), such as tables backed by Google Sheets or Cloud Storage, the service account also needs the `storage.objects.get` and `storage.objects.list` permissions.

## Size limit for views and SQL queries

Felt reads a BigQuery view or [SQL query](/upload-anything/sql-queries.md) by running a query, and BigQuery limits query results to 10 GB. For a larger result, filter the view or query to return less data, or add the data from a table, which has no such limit.


---

# 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://help.felt.com/upload-anything/data-sources/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.