Skip to main content
Book a demo

Connect Google Sheets to Claude

Give Claude governed access to Google Sheets’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Google Sheets to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Google Sheets in Runlayer

    Add Google Sheets from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Google Sheets’s 21 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Google Sheets

    Sign in the way Google Sheets requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Google Sheets from Claude

    Google Sheets’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

21 Google Sheets tools in Claude

Runlayer policy decides which of these Claude users can call. 4 read data only and 4 can change or delete data.

  • Add sheet

    Add a new sheet (tab) to an existing spreadsheet.

  • Append

    Append data to a spreadsheet.

  • Autofill

    Extend a formula or detected series from a source range into a larger destination range (like dragging the fill handle).

  • Clear

    Clear the values in a range while leaving the rows, columns, and formatting in place.

  • Clear filter

    Remove a sheet's filter, restoring any rows it was hiding.

  • Create

    Create a new spreadsheet.

  • Create filter

    Turn on filtering over a range of a sheet (the funnel button in the Sheets UI), so rows can be sorted and filtered by column.

  • Delete rows

    Delete rows from a sheet, shifting the rows below them up.

See all 21 Google Sheets tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Google Sheets call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination