> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/data-and-assets/connections/bigquery.md). # BigQuery Connect to Google BigQuery with a service account key. ## Connection details A BigQuery connection uses a **Google Cloud service account key**: the JSON key file you download when you create a key for a service account. It includes the project ID, the service account's email and its private key. Enter the details from the key file when you create the connection. The private key is never shown again after you save it. ## Tips * Create a **dedicated service account** for Zerve, and grant it only the BigQuery roles it needs, such as BigQuery Data Viewer and BigQuery Job User for read-only work. * BigQuery charges for the data queries scan. Filter on partitioned columns where you can. See [Data connections](/zerve-docs/data-and-assets/connections.md) for creating, naming and attaching connections. --- # 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.zerve.ai/zerve-docs/data-and-assets/connections/bigquery.md?ask=&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.