> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/databases-and-warehouses/integrating-with-google-cloud-storage.md).

# Integrating with Google Cloud Storage

Connect Google Cloud Storage to Drivetrain and import object data into planning models. Covers service account setup and bucket permissions.

[Prerequisites](#prerequisites)

[Google Cloud Storage Setup](#google-cloud-storage-setup)\
[Step 1: Create a new bucket (optional)](#step-1-create-a-new-bucket-optional)\
[Step 2: Grant permissions to access the bucket](#step-2-grant-permissions-to-access-the-bucket)

## Prerequisites

To connect Google Cloud Storage to Drivetrain, you need:

* An active Google Cloud Storage account
* A Google Cloud Storage bucket and path of folder containing CSV files.

## Google Cloud Storage Setup <a href="#google-cloud-storage-setup" id="google-cloud-storage-setup"></a>

Drivetrain supports integration with Google Cloud Storage from a read-only external user account. To get started you would need to share the read-only access with <drivetrain@integrations-417606.iam.gserviceaccount.com> service account.

### Step 1 : Create a new bucket (optional) <a href="#step-1-create-a-new-bucket-optional" id="step-1-create-a-new-bucket-optional"></a>

{% hint style="info" %}
If you are granting read access to an existing bucket, proceed directly to Step 2.
{% endhint %}

1. Create a new bucket with name as "Drivetrain Bucket" with US multi region.
2. Create a new folder "Drivetrain Files" under this bucket and move all the CSV files you want to ingest into this folder.

### Step 2: Grant permissions to access the bucket <a href="#step-2-grant-permissions-to-access-the-bucket" id="step-2-grant-permissions-to-access-the-bucket"></a>

To grant an access to external user, (someone who is not listed as an employee in the company), follow these steps:

1. Log in to your Google Cloud account. Open Google Cloud Storage in the Cloud Console, then select the bucket containing the files you want to share.
2. Choose **Permissions** tab and click on **Grant Access**

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-564252123578f61aacf81f6feedcd78b73061021%2FGC-1.avif?alt=media" alt=""><figcaption></figcaption></figure>

3. Add <drivetrain@integrations-417606.iam.gserviceaccount.com> service account to the New principals and assign below mentioned roles and click **Save**
   1. **Storage Legacy Bucket Reader**
   2. **Storage Legacy Object Reader**

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-1f2b818f08f0485e23f2e1732a7dc4a914499261%2FGC-2.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
That’s it! Share the below details with your Customer Success Manager or Data Integrations Manager so that they can get started:

1. Bucket Name
2. Folder Path (where CSV files are stored)
   {% endhint %}


---

# 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://integrations.drivetrain.ai/integration-guide/readme/databases-and-warehouses/integrating-with-google-cloud-storage.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.