google-drive

Google Drive API integration with managed OAuth. List, search, create, and manage files and folders. Use this skill when users ask to find, read, share, organize, upload, or download files and folders in their own Google Drive — for example "find my Q3 budget sheet", "share this folder with alice@", "what changed in this doc". It handles files as whole objects — downloading or exporting their contents, and uploading or replacing the bytes. For editing *inside* a document — rewriting paragraphs, changing cells, editing slides — use the Google Docs, Sheets, or Slides skills instead. Not for Gmail attachments, and not for another user's Drive unless it is shared with the connected account. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Drive connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Drive action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Drive examples; they add no Google Drive capability - Google Drive is not an event source, a trigger cannot read Google Drive data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).