AI Workflows for Google Drive and Docs

AI on Google Drive is not “tidy the whole drive.” Split summaries and drafts per document, lock folder rules yourself, and keep link sharing as a human gate. This article does not list prices for Workspace add-ons.

Replace “summarize this Drive” with the S04 skeleton: goal, scope, done-check — applied to Docs/Drive.

How do you summarize and draft?

One-line answer: Lock the file ID/section scope and the output shape (bullets, decisions, open items). Take drafts only as a new doc or comments.

Inputs before the agent runs:

  • Target: file name/link and readable sections. Exclude HR, contracts, secrets.
  • Purpose: weekly share summary versus a one-page decision brief.
  • Format: decisions / open questions / actions (owner, due date).
  • Banned: overwriting the source Docs body; filling missing numbers by guess.

Sample instruction: “Read only the ‘Decisions’ through ‘Next week’ sections. Create a new Doc with an action table (owner, due, source paragraph). Do not edit the source. Missing dates → [needs check].”

A useful artifact:

  1. Pointers back to source sections or a short quote.
  2. Decisions not mixed with open questions.
  3. Draft separated from the source (file, tab, or comment thread).

Do not mix summary and full rewrite in one session. Read-only summary → agree → draft session.

How do you classify folders?

One-line answer: A person defines the tree and naming rules. The agent returns a proposal list only; bulk moves wait after sample approval.

If the model invents folders, you get misc and New folder (1). Write rules first:

  • Tree: e.g. 00-inbox / 10-active / 20-ref / 90-archive, depth two or three.
  • Names: YYYY-MM-DD_topic_version. State whether spaces/emoji are banned.
  • Ownership: shared drive versus My Drive; note paths where moves break ACLs.
  • Artifact: a move-proposal CSV (current → proposed → reason). No immediate moves.

Sample instruction: “List Docs/Sheets in 00-inbox only. Propose 10-active or 20-ref with a one-line reason. Do not move. If names break the rule, only suggest a new name.”

Sample done-check: “Proposal table of 20 rows, zero rule breaks at proposal time. After a person approves five samples, then bulk-move.”

Parallel agents must read the same tree doc. If each creates folders, Drive gets worse.

What about permissions and sharing?

One-line answer: A person checks link scope, viewer/editor roles, and external domains. Do not give the agent permission to change ACLs or create public links.

Human gates:

  • Links: org-only / anyone with link / public. Default-reject “make it public for convenience.”
  • Roles: viewer, commenter, editor. Commenter is often enough for draft review.
  • External: customer/vendor domains. Keep contracts and PII in a summary-only folder when sharing out.
  • Agent scopes: when attaching Drive API/MCP, prefer read-only for summary sessions; separate write sessions.
  • Lifecycle: expire temporary links; reassign files owned by departed accounts.

Add-on plan prices move on vendor pages, so they are not frozen here. Prefer tools that keep drafts off the source and require a human to approve sharing changes.

Minimum path: (1) exclusion list and summary template, (2) draft in a new doc, (3) folder proposals → sample approve → move, (4) sharing only by a person. If the agent says “all tidy,” do not skip 4.

On Drive, permission is the security boundary. Delegating sharing before classification costs more than search-only habits.

Sources

  • S03/S04 applied to Docs/Drive artifacts.
  • Google Workspace and add-on pricing: official pages (not pinned here).