Google Sheets

Independent, unofficial connector for Google Sheets. Not affiliated with, endorsed by, or sponsored by Google Sheets. "Google Sheets" is a trademark of its owner, used only to identify the service this connector works with.

Tools for working with Google Sheets against the Google Sheets API v4 (https://sheets.googleapis.com/v4/), with spreadsheet discovery via the Google Drive API. 26 tools across two complementary surfaces: a record surface — rows as objects keyed by their column headers (the "log this expense", "update the status to Done", "look up last quarter's total" jobs) — and a cell surface — raw A1-addressed values for formulas, precise numeric/text control, and arbitrary ranges. Plus spreadsheet/worksheet structure and presentation (formatting, sorting, validation).

When to use this

• Read or find data inside a spreadsheet — look up a row by a column value (lookupRow), find all matching rows (findRows), list a window of rows (listRows), or read a raw range (getValues).
• Write data — append a row or many rows (createRow / createRows), update specific columns of a row without disturbing the others (updateRow / updateRows), or write a raw range / formula (updateValues).
• Clear or delete — clear a row's contents but keep the row (clearRows / clearValues) or remove rows entirely (deleteRows).
• Manage structure — create a spreadsheet (createSpreadsheet), add / list / copy / rename / hide / delete worksheets, add columns.
• Format & validate — number/date/currency formats, text styling, sort a range, copy a range, dropdowns and number/date validation, conditional formatting.

Setup

This is an agentskills.io skill.

If the connector has not been installed as a skill yet, install it first with npx skills add zapier/connectors --skill google-sheets (or your harness's own skill-install mechanism), then continue here. Installing the skill copies these files, not dependencies. Before running the CLI, a local MCP server, or zapier-sdk auth commands, run npm install --omit=dev here once. Importing the published package as a dependency in your own project instead? That npm install already resolves everything — see references/use-as-sdk.md.