> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/files-and-tables/google-big-query/how-to-get-google-cloud-key-file.md).

# How to get Google Cloud key file?

Learn how to generate a Google Cloud JSON key file to use for connecting Coupler.io to your BigQuery source or destination.

* Go to the [Google Cloud Platform console](https://console.cloud.google.com/).
* On the left-hand side of the activity dashboard, pick IAM & Admin.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee079b8556b07a2884f6f2/file-xVxcham7qG.png)

* Then on the left-hand side of the *IAM & Admin* page, pick Service Accounts.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee076a9e87cb3d0124d187/file-BRDewirsd2.png)

* Click Create service account at the top to add a new service account.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee055161c60c534bd6f4e7/file-cDylSbcDtm.png)

* Enter the Service account name and press Create.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee04fd8556b07a2884f6e1/file-qEIlnWqb9H.png)

* Add roles:

If you are setting up BigQuery as a source in [Coupler.io](http://coupler.io) (you only plan to grab data *from* BigQuery):

* *BigQuery Data Viewer*
* *BigQuery Job User*

If you are setting up BigQuery as a destination in [Coupler.io](http://coupler.io) (or plan to use it both as a source and as a destination):

* *BigQuery Data Editor*
* *BigQuery Job User*
* Click Continue, Done.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee04b59e87cb3d0124d171/file-hB7paHcjUs.png)

* Find your service account and open it.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee06388556b07a2884f6eb/file-ry0aZ8Wbmc.png)

* Navigate to the Keys tab

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee066461c60c534bd6f4f6/file-dNgkV7b37Y.png)

* Click "Add key", select the option "**Create new key**".

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee06ce8556b07a2884f6ed/file-ZDgo21L1lR.png)

* Pick JSON type and press Create.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee07e700fd0d7c253ffad8/file-FNeM4VbqNa.png)

* You will be asked to save a file to your computer. Save it.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/57fbf3029033600277a688ab/images/60ee086f00fd0d7c253ffadf/file-a1VKScuMRZ.png)


---

# 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.coupler.io/sources/category/files-and-tables/google-big-query/how-to-get-google-cloud-key-file.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.