> **Building with AI coding agents?** If you're using an AI coding agent, install the official Scalekit plugin. It gives your agent full awareness of the Scalekit API — reducing hallucinations and enabling faster, more accurate code generation.
>
> - **Claude Code**: `/plugin marketplace add scalekit-inc/claude-code-authstack` then `/plugin install <auth-type>@scalekit-auth-stack`
> - **GitHub Copilot CLI**: `copilot plugin marketplace add scalekit-inc/github-copilot-authstack` then `copilot plugin install <auth-type>@scalekit-auth-stack`
> - **Codex**: run the bash installer, restart, then open Plugin Directory and enable `<auth-type>`
> - **Skills CLI** (Windsurf, Cline, 40+ agents): `npx skills add scalekit-inc/skills --list` then `--skill <skill-name>`
>
> `<auth-type>` / `<skill-name>`: `agentkit`, `full-stack-auth`, `mcp-auth`, `modular-sso`, `modular-scim` — [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Google Docs

**Authentication:** OAuth 2.0
**Categories:** Files, Documents
## What you can do

Connect this agent connector to let your agent:

- **List list** — List all Google Docs documents in the user's Drive
- **Update update** — Update the content of an existing Google Doc using batch update requests
- **Read read** — Read the complete content and structure of a Google Doc including text, formatting, tables, and metadata
- **Create create** — Create a new blank Google Doc with an optional title

## Authentication

This connector uses **OAuth 2.0**. Scalekit acts as the OAuth client: it redirects your user to Google Docs, obtains an access token, and automatically refreshes it before it expires. Your agent code never handles tokens directly — you only pass a `connectionName` and a user `identifier`.

You supply your Google Docs **Connected App** credentials (Client ID + Secret) once per environment in the Scalekit dashboard.

Before calling this connector from your code, create the Google Docs connection in **AgentKit** > **Connections** and copy the exact **Connection name** from that connection into your code. The value in code must match the dashboard exactly.

## Set up the connector

Register your Scalekit environment with the Google Docs connector so Scalekit handles the authentication flow and token lifecycle for you. The connection name you create will be used to identify and invoke the connection programmatically. Then complete the configuration in your application as follows:

> caution
>
> Google applications using scopes that permit access to certain user data must complete a verification process.

1. ### Set up auth redirects

    - In [Scalekit dashboard](https://app.scalekit.com), go to **AgentKit** > **Connections** > **Create Connection**. Find **Google Docs** and click **Create**. Click **Use your own credentials** and copy the redirect URI. It looks like `https:///sso/v1/oauth//callback`.

      > Image: Copy redirect URI from Scalekit dashboard

    - Navigate to [Google Cloud Console](https://console.cloud.google.com/projectselector2/home/dashboard?supportedpurview=project) → **APIs & Services** → **Credentials**. Select **+ Create Credentials**, then **OAuth client ID**. Choose **Web application** from the Application type menu.

      > Image: Select Web Application in Google OAuth settings

    - Under **Authorized redirect URIs**, click **+ Add URI**, paste the redirect URI, and click **Create**.

      > Image: Add authorized redirect URI in Google Cloud Console

2. ### Enable the Google Docs API

    - In [Google Cloud Console](https://console.cloud.google.com/projectselector2/home/dashboard?supportedpurview=project), go to **APIs & Services** → **Library**. Search for "Google Docs API" and click **Enable**.

3. ### Get client credentials

    - Google provides your Client ID and Client Secret after you create the OAuth client ID in step 1.

4. ### Add credentials in Scalekit

    - In [Scalekit dashboard](https://app.scalekit.com), go to **AgentKit** > **Connections** and open the connection you created.
    - Enter your credentials:
      - Client ID (from above)
      - Client Secret (from above)
      - Permissions (scopes — see [Google API Scopes reference](https://developers.google.com/identity/protocols/oauth2/scopes))

      > Image: Add credentials in Scalekit dashboard
    - Click **Save**.

## Code examples

Connect a user's Google Docs account and make API calls on their behalf — Scalekit handles OAuth and token management automatically.

You can interact with Google Docs in two ways — via direct proxy API calls or via Scalekit optimized tool calls. Scroll down to see the list of available Scalekit tools.

## Proxy API Calls

  ### Node.js

```typescript

const connectionName = 'google_docs'; // get your connection name from connection configurations
const identifier = 'user_123';        // your unique user identifier

// Get your credentials from app.scalekit.com → Developers → Settings → API Credentials
const scalekit = new ScalekitClient(
  process.env.SCALEKIT_ENV_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET
);
const actions = scalekit.actions;

// Authenticate the user
const { link } = await actions.getAuthorizationLink({
  connectionName,
  identifier,
});
console.log('🔗 Authorize Google Docs:', link); // present this link to your user for authorization, or click it yourself for testing
process.stdout.write('Press Enter after authorizing...');
await new Promise(r => process.stdin.once('data', r));

// Make a request via Scalekit proxy
const result = await actions.request({
  connectionName,
  identifier,
  path: '/v1/documents',
  method: 'GET',
});
console.log(result);
```

  ### Python

```python

from dotenv import load_dotenv
load_dotenv()

connection_name = "google_docs"  # get your connection name from connection configurations
identifier = "user_123"          # your unique user identifier

# Get your credentials from app.scalekit.com → Developers → Settings → API Credentials
scalekit_client = scalekit.client.ScalekitClient(
    client_id=os.getenv("SCALEKIT_CLIENT_ID"),
    client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
    env_url=os.getenv("SCALEKIT_ENV_URL"),
)
actions = scalekit_client.actions

# Authenticate the user
link_response = actions.get_authorization_link(
    connection_name=connection_name,
    identifier=identifier
)
# present this link to your user for authorization, or click it yourself for testing
print("🔗 Authorize Google Docs:", link_response.link)
input("Press Enter after authorizing...")

# Make a request via Scalekit proxy
result = actions.request(
    connection_name=connection_name,
    identifier=identifier,
    path="/v1/documents",
    method="GET"
)
print(result)
```

## Scalekit Tools

## `googledocs_create_document`

Create a new blank Google Doc with an optional title. Returns the new document's ID and metadata.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `schema_version` | string | No | Optional schema version to use for tool execution |
| `title` | string | No | Title of the new document |
| `tool_version` | string | No | Optional tool version to use for execution |

## `googledocs_read_document`

Read the complete content and structure of a Google Doc including text, formatting, tables, and metadata.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `document_id` | string | Yes | The ID of the Google Doc to read |
| `schema_version` | string | No | Optional schema version to use for tool execution |
| `suggestions_view_mode` | string | No | How suggestions are rendered in the response |
| `tool_version` | string | No | Optional tool version to use for execution |

## `googledocs_update_document`

Update the content of an existing Google Doc using batch update requests. Supports inserting and deleting text, formatting, tables, and other document elements.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `document_id` | string | Yes | The ID of the Google Doc to update |
| `requests` | `array<object>` | Yes | Array of update requests to apply to the document |
| `schema_version` | string | No | Optional schema version to use for tool execution |
| `tool_version` | string | No | Optional tool version to use for execution |
| `write_control` | `object` | No | Optional write control for revision management |

## Tool list

Use the exact tool names from the **Tool list** below when you call `execute_tool`. If you're not sure which name to use, list the tools available for the current user first.

## Tool list

### `googledocs_create_document`

Create a new blank Google Doc with an optional title. Returns the new document's ID and metadata.

Parameters:

- `schema_version` (`string`, optional): Optional schema version to use for tool execution
- `title` (`string`, optional): Title of the new document
- `tool_version` (`string`, optional): Optional tool version to use for execution

### `googledocs_list_documents`

List all Google Docs documents in the user's Drive. Optionally search by document name. Returns document IDs, names, and metadata with pagination support.

Parameters:

- `order_by` (`string`, optional): Sort order for results. Examples: modifiedTime desc, name asc, createdTime desc
- `page_size` (`integer`, optional): Number of documents to return per page (max 1000, default 100)
- `page_token` (`string`, optional): Token for retrieving the next page of results. Use the nextPageToken from a previous response.
- `query` (`string`, optional): Drive search query to filter documents. Defaults to all Google Docs. To search by name, use: mimeType = 'application/vnd.google-apps.document' and trashed = false and name contains 'report'

### `googledocs_read_document`

Read the complete content and structure of a Google Doc including text, formatting, tables, and metadata.

Parameters:

- `document_id` (`string`, required): The ID of the Google Doc to read
- `schema_version` (`string`, optional): Optional schema version to use for tool execution
- `suggestions_view_mode` (`string`, optional): How suggestions are rendered in the response
- `tool_version` (`string`, optional): Optional tool version to use for execution

### `googledocs_update_document`

Update the content of an existing Google Doc using batch update requests. Supports inserting and deleting text, formatting, tables, and other document elements.

Parameters:

- `document_id` (`string`, required): The ID of the Google Doc to update
- `requests` (`array`, required): Array of update requests to apply to the document
- `schema_version` (`string`, optional): Optional schema version to use for tool execution
- `tool_version` (`string`, optional): Optional tool version to use for execution
- `write_control` (`object`, optional): Optional write control for revision management


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |