stevehuang0115/crewly/drive-search

Drive Search

bash execute.sh --query "Q3 plan"                 # names + full text, newest first
bash execute.sh --mime sheet --max 5              # 5 most recent spreadsheets
bash execute.sh --folder 1AbC... --query budget   # inside one folder

Output

{"count":1,"files":[{"id":"1x…","name":"Q3 plan","mimeType":"application/vnd.google-apps.document","modifiedTime":"…","webViewLink":"https://…","owners":["ann@example.com"]}]}

mimeType tells you which skill reads it: …document → docs-read, …spreadsheet → sheets-read, …presentation → slides-read, anything else → drive-read.

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.