What are the core workflows this skill supports?

This skill supports five core workflows: reading/writing data via batch operations, creating and managing spreadsheets and tabs, searching and filtering rows, upserting rows by a key column, and formatting cells. All operations are performed through Composio's Google Sheets toolkit exposed via Rube MCP.

What setup is required before using this skill?

You must add `https://rube.app/mcp` as an MCP server, verify that `RUBE_SEARCH_TOOLS` responds, call `RUBE_MANAGE_CONNECTIONS` with the `googlesheets` toolkit, and complete the Google OAuth link to activate the connection. No API keys are needed.

How do I upsert rows in Google Sheets using this skill?

Use `GOOGLESHEETS_UPSERT_ROWS` with a key column specified by its actual header name (e.g., 'Email' or 'SKU'), not a column letter. The `strictMode` parameter will error on mismatched column counts and automatically add missing columns as needed.

What format do color values need to be in when formatting cells?

Color values must be specified as 0.0-1.0 float color channels rather than 0-255 integers. Additionally, you must use the numeric `worksheet_id` (obtained from `GOOGLESHEETS_GET_SPREADSHEET_INFO`) rather than the tab title when formatting cells.

Skill

Automate Google Sheets Operations

Name: Google Sheets Automation via Rube MCP
Availability: OnlineOnly
Author: Antigravity

Automates Google Sheets read/write, tab management, filtering, upserts, and cell formatting through Composio's toolkit via Rube MCP.

Get skill

Works with google sheets

Antigravity

Own this? Claim it

Spark score

out of 100

Updated last month

Version 13.1.1

Models

universal

Add to Favorites

Why it matters

Streamline your Google Sheets management by automating data reading, writing, and spreadsheet manipulation. This asset enables efficient data handling and workflow automation directly within your Google Sheets environment.

Outcomes

What it gets done

Read and write data to Google Sheets

Create, rename, and manage spreadsheet tabs

Search and filter rows based on specific criteria

Upsert rows by a unique key column

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-googlesheets-automation | bash

Overview

Google Sheets Automation via Rube MCP

Documents how to automate Google Sheets read/write, spreadsheet/tab management, row search and filtering, key-based upserts, and cell formatting through Composio's toolkit over Rube MCP, with exact tool sequences and parameters for each. Use when automating Google Sheets data, tabs, filtering, upserts, or formatting via Rube MCP with an active Google Sheets connection already in place.

What it does

Automates Google Sheets workflows - reading and writing data, managing spreadsheets and tabs, formatting cells, filtering rows, and upserting records by key - through Composio's Google Sheets toolkit exposed via Rube MCP. It documents exact tool sequences, required parameters, and the sharp edges (locale-dependent tab names, 2D array requirements, rate limits) needed to drive Sheets correctly.

When to use - and when NOT to

Use this skill when a task requires reading/writing Google Sheets data, creating or managing spreadsheets and tabs, searching/filtering rows, upserting records by a key column, or formatting cells. It assumes Rube MCP is already connected (RUBE_SEARCH_TOOLS available) and the Google Sheets connection is ACTIVE via RUBE_MANAGE_CONNECTIONS - always call RUBE_SEARCH_TOOLS first to get current tool schemas. Do not use it without that active connection in place.

Inputs and outputs

Setup: add https://rube.app/mcp as an MCP server (no API keys needed), verify RUBE_SEARCH_TOOLS responds, call RUBE_MANAGE_CONNECTIONS with toolkit googlesheets, and complete the Google OAuth link if not already ACTIVE.

Five core workflows: Read/write data via GOOGLESHEETS_BATCH_GET/GOOGLESHEETS_BATCH_UPDATE (values as 2D arrays, valueInputOption of USER_ENTERED vs RAW, always bounded ranges to avoid timeouts on sheets over 10,000 rows). Create/manage spreadsheets via GOOGLESHEETS_CREATE_GOOGLE_SHEET1, GOOGLESHEETS_ADD_SHEET, and GOOGLESHEETS_UPDATE_SHEET_PROPERTIES (unique tab names, locale-dependent defaults like 'Sheet1' vs 'Hoja 1', avoiding parallel index writes). Search/filter rows via GOOGLESHEETS_LOOKUP_SPREADSHEET_ROW (exact full-cell match, not substring) and GOOGLESHEETS_SET_BASIC_FILTER/CLEAR_BASIC_FILTER. Upsert rows by key via GOOGLESHEETS_UPSERT_ROWS, keyed on an actual header name like 'Email' or 'SKU' (not a column letter), with strictMode erroring on mismatched column counts and auto-adding missing columns. Format cells via GOOGLESHEETS_FORMAT_CELL, which needs the numeric worksheet_id (from GOOGLESHEETS_GET_SPREADSHEET_INFO), not the tab title, and 0.0-1.0 float color channels rather than 0-255 integers.

Known pitfalls preserved from the source: sheet names with spaces need single quotes in A1 notation ('My Sheet'!A:Z); all value parameters must be lists of lists even for a single row; Google Sheets enforces roughly 60 reads/minute and 60 writes/minute, so batch operations to stay within limits; and GOOGLESHEETS_DELETE_DIMENSION is irreversible, so bounds must be double-checked before calling it.

Integrations

Runs entirely through Rube MCP (https://rube.app/mcp) and Composio's Google Sheets toolkit - RUBE_SEARCH_TOOLS for schema discovery and RUBE_MANAGE_CONNECTIONS for the Google OAuth connection, with no separate Google Cloud credential setup required.

Who it's for

Ops and automation builders who need to drive Google Sheets read/write, tab management, filtering, upsert, and formatting workflows through Composio/Rube MCP tools correctly - especially around the rate limits, locale quirks, and 2D-array/numeric-ID requirements that are easy to get wrong from the raw Sheets API alone.

FAQ

Common questions

Discussion