> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adside.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google

> Google Sheets/Drive REST endpoints and Google Ads MCP tools

# Google

Google integration includes two parts:

* **Google Sheets/Drive** — 5 REST endpoints for spreadsheet and file operations
* **Google Ads** — MCP tools for ad campaign management

## Google Sheets & Drive (REST)

These are standard REST endpoints (not MCP tools):

| Endpoint                                      | Method | Description                                                                 |
| --------------------------------------------- | ------ | --------------------------------------------------------------------------- |
| `/google/sheets/meta-bulk-upload/read`        | GET    | Read the Meta bulk-upload Google Sheets template                            |
| `/google/sheets/video-generation-cities/read` | GET    | Read a GOATS-96 city sheet with a `Cities` tab and a required `city` column |
| `/google/sheets/meta-bulk-upload/write`       | POST   | Write bulk-upload results back to the Meta bulk-upload sheet                |
| `/google/drive/files`                         | GET    | List or retrieve Google Drive files                                         |
| `/google/drive/upload-to-meta`                | POST   | Upload a Drive file to Meta Ads Manager                                     |

### Cross-source operations

`/google/drive/upload-to-meta` requires **both** Google and Meta channels connected in your API key. If Meta is not connected, you'll get a `403` error.

## Google Ads (MCP)

Google Ads tools are accessed via `POST /google-ads/mcp` using the standard MCP protocol.

## Prerequisites

* A [Google Cloud Console](https://console.cloud.google.com/) project with the relevant APIs enabled
* OAuth 2.0 credentials (access token + refresh token)
* For Google Ads: a developer token and customer/account ID

## Authentication

Google uses OAuth 2.0. Both `accessToken` and `refreshToken` are stored in your API key's channel credentials under the `google-ads` key.