mcp intermediate active

Google Sheets

Agent outputs disappear unless logged. Google Sheets stores them permanently.

What breaks without openclaw google sheets skill

Data logged manually. Append vs update confusion wiping rows. A1 notation mismatched.

Full Google Sheets read/write × 220-star trusted skill ÷ 20–30 minutes ÷ OAuth scope only = living data pipeline in your spreadsheet.

openclaw google sheets skill — what it actually does

01
Reads from and writes to Google Sheets in OpenClaw pipelines
02
Uses Sheets as a lightweight database or logging target
03
Appends new rows without overwriting existing data
04
Targets cells with A1 notation — /sheets read Sheet1!A1:C10
05
Authenticates once via /sheets auth and persists credentials

Security check — openclaw google sheets skill

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.0 compatibility.

Quick start — openclaw google sheets skill in 20–30 minutes

Setup time: 20–30 minutes

!
You need:
  • OpenClaw core
  • Sheets API enabled
  • OAuth credentials

Install the package:

clawhub install byungkyu/google-sheets
1
Enable Sheets API in Google Cloud Console
2
Authenticate with /sheets auth
3
Run /sheets read <spreadsheet-id> Sheet1!A1:C10
4
Run /sheets write to update cells

Troubleshooting openclaw google sheets skill

1
1. Append vs update — use correct operation for logs vs overwrite use cases
2
2. Column letters vs indices — skill uses A1 notation exclusively

Compatibility & status

Works with: Linux, macOS; OpenClaw ≥1.0 intermediate Last updated: Nov 2025 ★ 220 on GitHub MIT

Official docs →

View on GitHub →

Related — more like openclaw google sheets skill

More by byungkyu

Every agent output without a log is data your team can never audit. Install before the next pipeline run produces untracked results.

Get it on GitHub →