Connect Google Sheets to Claude Cowork
Give Claude Cowork governed access to Google Sheets’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Sheets to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 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
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Google Sheets’s 21 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 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
Use Google Sheets from Claude Cowork
Google Sheets’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
21 Google Sheets tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork 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.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Google Sheets call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork 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)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more