Free to read · no account needed

16 min · plugins

Connectors: Drive, mail, calendar

Goal: connect everyday work apps with beginner-safe defaults.

Best for: first connections to Google Drive / mail / calendar-style apps inside ChatGPT, Claude, or similar.

Connectors link the model to your files and inbox. Powerful = easy to overshare. Start read-only where possible; create a sandbox folder; never connect a personal vault of secrets on day one.

Click path (typical): Settings or Tools → Connectors / Apps → choose provider → Allow minimal scopes → run a read-only test.

Connect the boring three only after you can name the weekly job. Prefer read or draft scopes; treat send/write as a separate decision.

Why beginners skip this

Connecting Drive, mail, and calendar all at once feels powerful until a draft auto-sends or a write hits the wrong folder. Beginner-safe defaults are read-first and ask-before-send.

Habit this week (Asia/Shanghai): revoke one unused connector scope and set send/write to ask-every-time; date the change.

Step 1 — Sandbox folder first (Drive)

Create AI-Sandbox/ in Drive. Only connect or point the tool at that folder if the product allows narrowing.

Write a beginner setup checklist for Drive connector with a sandbox folder.
Include: folder name · what goes in · what stays out · first test prompt.
Example

Filled prompt

Live task this week (not a toy): apply this guide's Goal — connect everyday work apps with beginner-safe defaults.
Fill with your real artifact names/files. Constraints: no invented facts; label Unknowns; stop before send/delete/pay.
Return the working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Scopes match least need for “connect everyday work apps with beginner-safe defa”
  • Draft preferred; send is ask-every-time
  • Unused write revoked or scheduled
  • Pass/fail: one scope change logged
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Step 2 — Mail: draft, don’t send

If mail connect is on: instructions must say drafts only until you click send in the real mail app.

Write agent/skill rules (≤10 bullets) for a mail connector: draft-only, no send, no delete, summarize unread with subjects only.
Example

Filled prompt

I connected Drive read + Gmail send "for convenience."
Rewrite scopes for least privilege this month: I only need Drive read + Gmail draft.
Ask-every-time on send. Return before/after.

What good output looks like

  • Draft preferred; send is ask-every-time
  • Unused write revoked or scheduled
  • Pass/fail: one scope change logged
  • Scopes match least need for “connect everyday work apps with beginner-safe defa”

Step 3 — Calendar: create with confirmation

Allow read freely if needed; creating events requires listing details for your OK first.

Prompt template: propose a calendar event as a draft card (title, time, guests, location) and wait for YES before create.
Example

Filled prompt

Draft card for 30-min sync Tue 10:00 with Alex; wait for YES.
Context: live job for connectors-drive-mail-calendar — “connect everyday work apps with beginner-safe.” Keep never-invent / draft-only.

What good output looks like

  • Unused write revoked or scheduled
  • Scopes match least need for “connect everyday work apps with beginner-safe defa”
  • Pass/fail: one scope change logged
  • Draft preferred; send is ask-every-time

Save this card

Card: read-first · draft-ok · send/write ask-every-time · revoke unused scopes monthly.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open Drive/Mail/Calendar permission panels. List what “connect everyday work apps with beginner-safe defaults” truly needs. Revoke candidates ready before you click Allow Guide: connectors-drive-mail-calendar Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week: review scopes for “connect everyday work apps with.” Revoke one unused write; send stays ask-every-time. on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed connectors-drive-mail-calendar, put 25 minutes on the calendar and redo once.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Stage the three

Connect calendar read before mail send. Boredom in week one is success.

Red flag

Default send allowed; shared drive writable to the model; cannot list permissions—revoke and reopen read-only.

Pitfalls

PitfallFix
Calendar write for “just listing”Demand read-only scope
Sandbox folder forgottenCreate AI-sandbox before first write
Connecting entire Drive rootSandbox folder
Send scope “for convenience”Draft-only
Leaving connectors on unused accountsDisconnect
Example

Filled prompt

Temptation: skip the habit for connectors-drive-mail-calendar to “save five minutes.”
Job still: connect everyday work apps with
Do the smallest correct pass: Done visible · one checkable artifact · Unknowns labeled [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: the artifact + the refuse-line you said aloud.

What good output looks like

  • Names the shortcut you refused (specific to connectors-drive-mail-calendar)
  • Still delivers a checkable artifact for “Connectors: Drive, mail, calendar”
  • Unknowns labeled; draft-only respected
  • Pass/fail: refuse-line written and dated (connectors-drive-mail-calendar #4)

Practice now

Live card: screenshot or list scopes for one connector; delete one scope you cannot defend (Asia/Shanghai).

Audit one connector: keep read-only for demos; require human confirm for send/calendar writes. Turn off one unused write scope today (Asia/Shanghai).

Connector audit card (copy):

  • Connector: Drive / Mail / Calendar / other: ___
  • Scopes today: read ___ · draft ___ · send/write ___
  • Unused write scope to revoke: ___ · revoked? Y/N (date: ___)
  • Human-confirm rule for send/calendar: stated in ___ (team note / personal rule)

Demo rule: if the task is “show me,” stay read-only. If the task is “send/schedule,” stop for a human click.

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Connectors default to read/draft; send and write stay ask-every-time. This week: revoke one unused scope and date the change (Asia/Shanghai).

Next

Tools and approvals · Blast radius · Least-privilege checklist · Secrets and pasting · PII redaction habits

Pair with today: open the first Next link (mcp-tools-permissions-and-approvals) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start