> ## Documentation Index
> Fetch the complete documentation index at: https://ampersand-24eb5c1a-rajatspawar-eng-4200-readd-blob-storage.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Cloud Storage destinations

For more information on destinations, see the [Destinations](/destinations) page.

When new data is read from a SaaS instance via a [Read Action](/read-actions) or [Subscribe Action](/subscribe-actions), Ampersand writes the payload as objects to your Google Cloud Storage bucket.

## Prerequisites

Before setting up a Google Cloud Storage destination, ensure that you have:

* A Google Cloud project with a Cloud Storage bucket
* A service account with the `Storage Object Creator` role (or `storage.objects.create` permission) on that bucket, and a JSON key for it

## Data format

Ampersand writes each read or subscribe message as a JSON object to your bucket. The full payload schema is defined in [webhook.yaml](https://github.com/amp-labs/openapi/blob/main/webhook/webhook.yaml).

## Create a Google Cloud Storage destination

Go to the [Destinations page](https://dashboard.withampersand.com/projects/_/destinations) in the Ampersand Dashboard and create a new Google Cloud Storage destination.

You'll need to provide:

| Field                           | Type   | Required | Example                        | Description                                              |
| ------------------------------- | ------ | -------- | ------------------------------ | -------------------------------------------------------- |
| **Destination name**            | string | Yes      | `ampersandGCS`                 | Alias to reference in your `amp.yaml` file               |
| **Bucket**                      | string | Yes      | `ampersand-integration-bucket` | Name of your Cloud Storage bucket                        |
| **Service account credentials** | string | Yes      |                                | Service account key JSON with write access to the bucket |

## Refer to the destination in your integration

After creating your Google Cloud Storage destination, reference it in your `amp.yaml` file:

```yaml theme={null}
specVersion: 1.0.0
integrations:
  - name: salesforceToGCS
    displayName: Salesforce to Google Cloud Storage
    provider: salesforce
    read:
      objects:
        - objectName: account
          destination: ampersandGCS
        - objectName: contact
          destination: ampersandGCS
```