Section 01 — Why this matters

Your fixture list is in Google Sheets. Your training plans are in Drive. Your player database is in Notion. Your GPS exports live in a folder you forget about. Claude can now read all four of them directly — no copy-paste, no exports — through one-click OAuth connectors. This is the setup that turns Claude from a chatbot into a workspace assistant. Tier: Free Claude plan with directory connectors works for the basics.

Section 02 — What this actually upgrades

A integration tool, not a notes tool. The distinction matters.

Layer · Integration

This upgrades the Integration layer. The data that defines your week is already digitised — it's just sitting in tools that don't talk to each other. Claude's connector directory bridges them via OAuth, so Claude reads your Drive and Notion the same way you do (with your permissions).

Cognitive load removed

It removes the 'switching between six tabs to answer one question' load. You ask one question and Claude pulls from all the sources at once.

Workflow slot

Set up once during a quiet hour. Maintenance is near-zero — connectors stay live as long as you stay logged in.

Section 03 — This week's upgrade

Three steps. Twelve minutes total.

Step 01
Install
In claude.ai, click your profile (bottom-left) → Settings → Connectors. You'll see a directory of 50+ integrations: Google Drive, Gmail, Notion, Asana, Linear, Jira, Slack, Canva, GitHub, more. These are OAuth, not custom servers — no JSON, no terminal.
Step 02
Use once
Click Google Drive → Connect. Sign in with the Google account that holds your coaching folder. Grant read access. Repeat for Notion — connect the workspace that holds your player database. (Optional: add Gmail if you want Claude to draft replies for you, or Calendar to surface fixture conflicts.)
Step 03
Store
Test it. Open a chat in your Season Project. Ask: 'In my Notion player database, who has the most game time this season?' or 'In Google Drive, find the most recent training plan and summarise it.' Claude will tell you which connector it used and cite the source file.

Section 04 — The prompts

3 prompts, one unlocked.

▶ First test — confirm Drive is connectedClaude (any plan)

Search my Google Drive for the most recent file with 'training' in the name. Open it, summarise it in 5 bullets, and tell me which folder it lives in.

▶ First test — confirm Notion is connectedClaude (any plan)

Member-only prompt — click to unlock.

🔒 Member only

Free email account unlocks all prompts.

▶ Real workflow — Tuesday training plan generatorClaude (any plan)

Member-only prompt — click to unlock.

🔒 Member only

Free email account unlocks all prompts.

Section 05 — How each role uses it

Same tool. 3 different jobs.

Performance Ops

uses it as the audit and admin layer — Claude can answer 'when did we last update the fixture list?' without you opening the doc.

Head Coach

uses it to query training history without leaving Claude — 'what have we done on set-piece in the last fortnight?'

Performance Analyst

uses it to combine GPS exports (in Drive) with player records (in Notion) for a single combined view.

Section 06 — Who shouldn't use this

⚠ Skip this if

If your club's IT policy blocks third-party OAuth access to its Google Workspace or Notion, you can't enable this. Check with whoever owns admin rights before you sign up. (For solo coaches and clubs without strict IT controls, this is a non-issue.)

Section 07 — Stack position

Where this fits in the system.

← Pairs with

The Season Project — Claude as Your Tactical Second Brain

Capture · Layer 01

→ Feeds into

The Fireflies + Claude Meeting Brain (MCP Setup)

Memory · Layer 03

Section 08 — Leverage scorecard

The spec sheet.

Connect Google Drive + Notion to Claude in 5 Minutes · Integration

SOTG-08

7/ 10

Leverage Score

Time to install5 minutes

Time saved per week20 minutes of context-switching

Cognitive load removedMedium

AI literacy requiredLow

Free tier sufficientYes