stevehuang0115/crewly/drive-upload

Drive Upload

bash execute.sh --path ./report.pdf --folder 1Fo…            # binary-safe
bash execute.sh --path ./notes.md --convert doc               # becomes a Google Doc
bash execute.sh --name summary.txt --text "…" --folder 1Fo…

Output

{"success":true,"file":{"id":"1AbC…","name":"report.pdf","mimeType":"application/pdf","webViewLink":"https://…"}}

Limit: 10 MB per upload. Share the webViewLink with people (Drive permissions are the owner's — this skill does not change sharing).

Failures

{"success":false,"reason":"not_connected","hint":"<connect URL>"} (exit 1) when the owner has not connected Google Workspace. Run the google-connect skill to post the owner a one-tap card in Slack (never send them to Crewly settings or the Connections page — they are usually on a phone). Manual fallback: https://crewlyai.com/portal/integrations/google. A 403 with reason: "google_error" on a write means the file was not created by Crewly — the grant only edits files Crewly made (drive.file).

Choosing a Google account

Several Google accounts can be connected at once. Without --account the call uses the default one (the first you connected, or whichever the owner marked default). Name one explicitly when it matters:

bash execute.sh --account work@company.com ...

The account must be connected for this product — Google consent is per product (Gmail / Calendar / Drive), so an account connected only for Calendar cannot read Drive.