Uploading Reports to Drive and Sharing With Stakeholders — Zero Clicks

The Problem

The workflow was always the same. Agent generates a report. I download it. Open Google Drive. Navigate to the right folder. Upload. Right-click, share. Type email addresses. Set permissions. Copy the link. Paste it in Telegram or email.

Five minutes per file. Doesn't sound like much. But when you're generating 3-5 reports a week across investment scorecards, marketing case studies, portfolio analyses, and operational backups, that's 15-25 minutes of pure friction. Clicking through a UI to move a file from point A to point B.

Worse: half the time I'd forget to share it. Or I'd upload to the wrong folder. Or I'd share with edit permissions when it should've been view-only. Small errors that compound into organizational chaos when you're running 31 agents generating outputs daily.

The Solution

The gog CLI's Drive capabilities, wired directly into agent workflows. When an agent finishes generating a report, the next step isn't "notify Bilal to upload it." The next step is: upload to the correct Drive folder, share with the relevant stakeholders, and send the link.

The agent maintains a folder taxonomy. It knows that investment scorecards go in /PyratzLabs/Reports/Scorecards/, that case studies go in /PyratzLabs/Content/Case Studies/, and that backups go in /mrchief-backups/. No ambiguity. No manual routing.

The Process

The upload pipeline is straightforward — the magic is in making it automatic:

# Upload a file to a specific Drive folder
gog drive upload ./output/q4-scorecard.pdf \
  --folder "Reports/Scorecards" \
  --name "Q4-2025-Investment-Scorecard.pdf"

# Share with specific people
gog drive share "Q4-2025-Investment-Scorecard.pdf" \
  --email "pierre@pyratzlabs.com" \
  --role viewer

gog drive share "Q4-2025-Investment-Scorecard.pdf" \
  --email "marc@investor.com" \
  --role viewer

# Get the shareable link
gog drive link "Q4-2025-Investment-Scorecard.pdf"

This is embedded in every report-generating workflow. Here's how it looks in an agent task:

- name: weekly-scorecard
  schedule: "0 9 * * 1"  # Monday 9am UTC
  task: |
    Generate the weekly investment scorecard:
    1. Pull portfolio data from the tracker
    2. Calculate performance metrics
    3. Generate the scorecard as PDF
    4. Upload to Drive: Reports/Scorecards/
    5. Share with Pierre (viewer) and the investment team (viewer)
    6. Send the Drive link to Bilal on Telegram with a one-line summary

The folder structure is maintained by convention, documented in the agent's context:

PyratzLabs (Drive Root)
├── Reports/
│   ├── Scorecards/        ← Investment performance scorecards
│   ├── Financial/         ← Warren's financial reports
│   └── Operations/        ← Operational metrics
├── Content/
│   ├── Case Studies/      ← Published case studies
│   ├── Articles/          ← Blog posts, thought pieces
│   └── Decks/             ← Pitch decks, presentations
├── Legal/
│   ├── Contracts/         ← Active agreements
│   └── Compliance/        ← Regulatory docs
└── mrchief-backups/      ← Agent config backups, memory snapshots

Real files that have gone through this pipeline:

# The 47-improvement article
gog drive upload ./output/47-improvements-article.md \
  --folder "Content/Articles"

# Case study batch uploads
gog drive upload ./output/case-studies-batch1.md \
  --folder "Content/Case Studies"

# Config backups
gog drive upload ./backups/mrchief-config-20260312.tar.gz \
  --folder "mrchief-backups"

The Results

The hidden win: consistency. Every report is named with the same convention, in the same folder, shared with the same permissions. Six months from now, when someone asks "where's the Q4 scorecard?", it's exactly where it should be. No archaeology required.

Try It Yourself

1. Set up gog with Drive access for your Google Workspace account
2. Define your folder taxonomy — write it down, not in your head
3. Start with one workflow: pick your most frequent report and automate the upload
4. Add sharing rules per folder (e.g., "everything in Reports/ shares with the leadership team")
5. Expand to all report-generating workflows once the pattern is proven

The key: don't think of Drive as a UI you visit. Think of it as a filesystem your agents write to. The upload is just another line in the pipeline.

Google Drive is a filesystem, not an app. My agents write to it like any other output directory. The stakeholders get their links. I never open drive.google.com.