Grok Bot + Google Sheets

How a Bot connects

Sheets API via the Bot's Google user, with specific spreadsheets shared to it.

The Bot's identity

Same Bot Google user as Workspace; sheets shared as editor only where it writes. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• Daily — append a row per completed routine run (the heartbeat log that catches silent failures)
• Weekly — KPI sheet refresh from CRM, Stripe and support exports
• On change — a 'requests' sheet humans fill in, the Bot picks up rows with status 'ready'

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

Overwriting ranges. Append, don't clear. Protected ranges for anything human-owned.

Verdict

The cheapest control plane there is. A requests sheet plus a heartbeat log gives you most of what an ops dashboard would.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the Google Sheets token in the Bot's connector settings or knowledge file, never in a chat message.