Skip to content
Talk to an Engineer Dashboard

Google Docs

Connect to Google Docs. Create, edit, and collaborate on documents

Connect to Google Docs. Create, edit, and collaborate on documents

Google Docs logo

Supports authentication: OAuth 2.0

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:

  1. Set up auth redirects

    • In Scalekit dashboard, go to Agent AuthCreate Connection. Find Google Docs and click Create. Click Use your own credentials and copy the redirect URI. It looks like https://<SCALEKIT_ENVIRONMENT_URL>/sso/v1/oauth/<CONNECTION_ID>/callback.

      Copy redirect URI from Scalekit dashboard

    • Navigate to Google Cloud ConsoleAPIs & ServicesCredentials. Select + Create Credentials, then OAuth client ID. Choose Web application from the Application type menu.

      Select Web Application in Google OAuth settings

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

      Add authorized redirect URI in Google Cloud Console

  2. Enable the Google Docs API

    • In Google Cloud Console, go to APIs & ServicesLibrary. 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, go to Agent AuthConnections and open the connection you created.

    • Enter your credentials:

      Add credentials in Scalekit dashboard

    • Click Save.

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

import { ScalekitClient } from '@scalekit-sdk/node';
import 'dotenv/config';
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);

Scalekit Tools

googledocs_create_document

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

NameTypeRequiredDescription
schema_versionstringNoOptional schema version to use for tool execution
titlestringNoTitle of the new document
tool_versionstringNoOptional 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.

NameTypeRequiredDescription
document_idstringYesThe ID of the Google Doc to read
schema_versionstringNoOptional schema version to use for tool execution
suggestions_view_modestringNoHow suggestions are rendered in the response
tool_versionstringNoOptional 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.

NameTypeRequiredDescription
document_idstringYesThe ID of the Google Doc to update
requestsarray<object>YesArray of update requests to apply to the document
schema_versionstringNoOptional schema version to use for tool execution
tool_versionstringNoOptional tool version to use for execution
write_controlobjectNoOptional write control for revision management

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

NameTypeRequiredDescription
schema_versionstringNoOptional schema version to use for tool execution
titlestringNoTitle of the new document
tool_versionstringNoOptional tool version to use for execution

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

NameTypeRequiredDescription
order_bystringNoSort order for results. Examples: modifiedTime desc, name asc, createdTime desc
page_sizeintegerNoNumber of documents to return per page (max 1000, default 100)
page_tokenstringNoToken for retrieving the next page of results. Use the nextPageToken from a previous response.
querystringNoDrive 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’

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

NameTypeRequiredDescription
document_idstringYesThe ID of the Google Doc to read
schema_versionstringNoOptional schema version to use for tool execution
suggestions_view_modestringNoHow suggestions are rendered in the response
tool_versionstringNoOptional tool version to use for execution

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

NameTypeRequiredDescription
document_idstringYesThe ID of the Google Doc to update
requestsarray<object>YesArray of update requests to apply to the document
schema_versionstringNoOptional schema version to use for tool execution
tool_versionstringNoOptional tool version to use for execution
write_controlobjectNoOptional write control for revision management