Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to Google Slides

Scalekit connector
Open markdown

The Google Slides connector lets your AI agent act in each user's Google Slides account. Each user signs in to Google Slides once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 5 tools.

Tools
5
What they doRead · write · destructive
3 · 2 · 03 read2 write0 destructive
Users sign in with
OAuth app
Your own Google app

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>
  3. Create the Google Slides connection

    In AgentKit > Connections, create a Google Slides connection and copy its redirect URI. The name you give it is the connection_name your code passes. See Configure connections.

  4. Register a Google OAuth app

    Google Slides connections use your own OAuth app. Register one with Google and add the redirect URI you copied.

    Then enter the app's Client ID and Client Secret on the Google Slides connection.

    Console steps with screenshots

    Register your Scalekit environment with the Google Slides 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 AgentKit > Connections > Create Connection. Find Google Slides 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 Console → APIs & Services → Credentials. 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 Slides API

      • In Google Cloud Console, go to APIs & Services → Library. Search for “Google Slides 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 AgentKit > Connections and open the connection you created.

      • Enter your credentials:

        Add credentials in Scalekit dashboard

      • Click Save.

  5. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    const scalekit = new ScalekitClient(
    process.env.SCALEKIT_ENVIRONMENT_URL,
    process.env.SCALEKIT_CLIENT_ID,
    process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    const connector = 'googleslides'
    const identifier = 'user_123'
    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Google Slides:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    // Make your first call
    const result = await actions.executeTool({
    connector,
    identifier,
    toolName: 'googleslides_read_presentation',
    toolInput: { presentation_id: 'YOUR_PRESENTATION_ID' },
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user signs in once. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • googleslides_get_pageGet the latest version of a single page (slide) within a Google Slides presentation, including its page elements, layout properties, and notes.Read-only

    Get Presentation Page

    Get the latest version of a single page (slide) within a Google Slides presentation, including its page elements, layout properties, and notes.

    Inputs

    page_object_idstringrequired
    The object ID of the page (slide) to retrieve
    presentation_idstringrequired
    The ID of the Google Slides presentation containing the page
    fieldsstring
    Fields to include in the response
  • googleslides_get_page_thumbnailGenerate and retrieve a thumbnail image URL for a single page (slide) in a Google Slides presentation.Read-only

    Get Page Thumbnail

    Generate and retrieve a thumbnail image URL for a single page (slide) in a Google Slides presentation. The returned content URL is temporary, valid for about 30 minutes.

    Inputs

    page_object_idstringrequired
    The object ID of the page (slide) to generate a thumbnail for
    presentation_idstringrequired
    The ID of the Google Slides presentation containing the page
    mime_typestring
    The image format of the thumbnailone of PNG
    thumbnail_sizestring
    The requested thumbnail image sizeone of THUMBNAIL_SIZE_UNSPECIFIEDLARGEMEDIUMSMALL
  • googleslides_read_presentationRead the complete structure and content of a Google Slides presentation including slides, text, images, shapes, and metadata.Read-only

    Read Google Slides

    Read the complete structure and content of a Google Slides presentation including slides, text, images, shapes, and metadata.

    Inputs

    presentation_idstringrequired
    The ID of the Google Slides presentation to read
    fieldsstring
    Fields to include in the response

    Also accepts schema_version and tool_version to pin a version.

  • googleslides_batch_update_presentationApply a batch of update requests to a Google Slides presentation in a single atomic call, such as inserting a slide, inserting text into a shape, creating a table, replacing text, or deleting an object.Write

    Batch Update Presentation

    Apply a batch of update requests to a Google Slides presentation in a single atomic call, such as inserting a slide, inserting text into a shape, creating a table, replacing text, or deleting an object. Returns the presentation ID and one reply per request, in the same order they were submitted.

    Inputs

    presentation_idstringrequired
    The ID of the Google Slides presentation to update
    requestsarrayrequired
    Ordered list of update requests to apply. Each item is a Slides API Request object, e.g. {"createSlide": {...}} or {"insertText": {...}}
    required_revision_idstring
    If set, the update is rejected unless the presentation's current revision ID matches this value, protecting against concurrent edits
  • googleslides_create_presentationCreate a new Google Slides presentation with an optional title.Write

    Create Presentation

    Create a new Google Slides presentation with an optional title.

    Inputs

    titlestring
    Title of the new presentation

    Also accepts schema_version and tool_version to pin a version.

Workflows

Proxy API call
const result = await actions.request({
connectionName: 'googleslides',
identifier: 'user_123',
path: '/v1/presentations',
method: 'GET',
});
console.log(result);
Execute a tool
const result = await actions.executeTool({
connector: 'googleslides',
identifier: 'user_123',
toolName: 'googleslides_create_presentation',
toolInput: {},
});
console.log(result);
Google OAuth consent screen verification

Before you use your own Google OAuth credentials in production, understand what end users see on Google’s consent screen when they authorize a connected account.

Audience typeConsent screen behaviorWhen to use
InternalShows your App Name and logo from Branding settingsOnly users in your Google Workspace or Cloud Identity organization can authorize the connector
ExternalShows {env_name}.scalekit.dev until Google verifies your appAny user with a Google account can authorize the connector

Why External is required for most AgentKit connectors:

  • Internal restricts authorization to users in your Google Workspace or Cloud Identity organization. Users with @gmail.com or other Google accounts outside your organization cannot complete OAuth.
  • External is required when end users outside your organization authorize tool access through connected accounts.
  • Organization-managed OAuth clients follow the same rules as personal or developer OAuth clients. Switching to an org-owned client does not bypass Google verification.
  • Until Google completes verification of your External app, users see scalekit.dev on the consent screen. After verification, your App Name and logo appear.

During development:

  • Add Test users under APIs & Services → OAuth consent screen while publishing status is Testing.
  • On unverified apps, users can click Advanced → Go to app (unsafe) to proceed during testing.
  • Google Workspace admins may need to allowlist your OAuth client.

For Google’s verification requirements and timeline, refer to Google’s OAuth consent screen verification guide.