What is a Cabinet?
Data
File types
Google Workspace pages

Google Workspace pages

A markdown page with a google: key in its frontmatter becomes a live iframe of a Google Sheet, Slide deck, Doc, or Form right inside Cabinet.

---
title: "Q3 OKR Tracker"
google:
  url: https://docs.google.com/spreadsheets/d/xxxxx/edit
  kind: sheet
---

Open the page — instead of the markdown body, Cabinet renders the embedded sheet. Click Open in Google in the toolbar to jump to the source for editing.

What it supports

kindSurface
sheetLive Google Sheet — view, navigate, sometimes edit (depends on the sheet's sharing)
docLive Google Doc
slideLive Slides deck — present mode supported
formLive Form (collect responses)

Why it works

Cabinet doesn't host inference and Cabinet doesn't host collaborative editing. Google does both well. The Google Workspace integration lets you keep live, collaborative, formula-rich documents as nodes in your cabinet tree — searchable in the sidebar, linked from your markdown notes, attached to agent tasks — without trying to reimplement Sheets or Docs.

Patterns

Tip. Use a Google Sheet for anything where formulas, charts, or pivot tables matter. Use a .csv for everything else — CSVs sit in your cabinet, syncs are simpler, agents can edit them directly.

Use a Google Sheet forUse a CSV for
Formulas, pivots, chartsAgent-edited row data (CRM, leads, content calendars)
Live collaboration with non-Cabinet usersAnything you want git-tracked
Sheets you already haveNew data tables

What agents see

By default, agents see only the metadata (title, URL, kind). To let an agent read the contents:

  1. Install the Google Workspace MCP server — it gives agents a gws.read_sheet / gws.read_doc tool.
  2. Authenticate the agent's persona with a service account or OAuth flow.
  3. The agent can now read_sheet({url: ...}) as part of a task.

Heads up. Granting an agent Google Workspace access is a real permission expansion. Treat it like granting any external API access — start tight, expand as needed.

Read on