> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/google-cloud.md).

# Google Cloud

## What is Google Cloud?

Google Cloud is Google's cloud computing platform, offering infrastructure, storage, and data/AI services that businesses use to run applications and manage data at scale. For this integration, the relevant component is Google Cloud Storage, Google's object storage service for storing and retrieving data of any size.

This method is for teams that already store or process data on Google Cloud and want their Coresignal datasets delivered directly to their Google Cloud Storage bucket, rather than downloading files manually via a web link.

## Available formats and delivery schedule

Coresignal delivers flat files, JSONL, Parquet, or CSV, depending on the dataset, to your chosen cloud storage service, such as S3, Azure, or GCS. All datasets are accessible according to your agreed schedule.

## How to connect Coresignal to Google Cloud?

Delivery to Google Cloud Storage is accomplished when you grant Coresignal access to their bucket, enabling direct file uploads.

{% stepper %}
{% step %}
**Send Google Cloud credentials and the bucket name**

You need to generate a service account key (a JSON file) for their Google Cloud project and securely send it to us. For information on service account keys, see [Google Cloud IAM docs](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#iam-service-account-keys-create-console). You must also provide the name of the Google Cloud Storage bucket where the files should be delivered.
{% endstep %}

{% step %}
**Confirm bucket permissions**

The service account associated with the JSON key must be able to create and list objects in the target bucket. `storage.objects.create` may be sufficient for a test upload, but recurring deliveries can fail without `storage.objects.list`, especially when files are delivered to dated paths or folders. We recommend granting a role that includes both permissions rather than creator-only access.
{% endstep %}

{% step %}
**Get notified once the first delivery is scheduled**

We will inform you when the initial files for the agreed datasets are ready. Data dumps will be sent according to your subscription schedule.
{% endstep %}
{% endstepper %}

## Verifying delivery

Once the first files land in your bucket, it's worth checking:

* **File presence** – the expected file(s) are present in the specified bucket/path.
* **Format correctness** – the file opens properly, and the schema matches the expected dataset.
* **File size** – the file volume looks in line with the dataset and is not empty.
* **Timestamp** – the delivery landed on the expected schedule, and the freshness or timestamp fields are recent, where available.

## FAQ

<details>

<summary>The upload failed – what's the most likely cause?</summary>

Usually, it is a permissions issue. Confirm that the service account in the JSON key has write access to the exact bucket name provided and that the key hasn't expired or been revoked on your end.

</details>

<details>

<summary>Can you deliver data to a specific path inside the bucket?</summary>

Yes, provide the full path (bucket name and folder structure) rather than just the bucket name, and we will configure the delivery job accordingly.

</details>

<details>

<summary>Can I have separate buckets for different datasets?</summary>

Yes, provide the bucket name for each dataset and confirm access. We will then set up individual deliveries to their respective buckets.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coresignal.com/integrations/google-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.