Skip to main content
Book a demo

Connect Google Sheets to Codex

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

Book a demo Codex setup guide

Set up

Add Google Sheets to Codex in four steps

Admins approve the server once. Everyone in Codex 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 Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Google Sheets’s 21 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex 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 Codex

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

Tools

21 Google Sheets tools in Codex

Runlayer policy decides which of these Codex 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 Codex

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination