Google Drive: purpose and common use cases
Google Drive is represented as a plugin from openai/plugins. Its catalog record points to plugins/google-drive and is grouped under Productivity and Presentations; install and source links are kept separate so the directory does not imply capabilities that are not present upstream.
Where Google Drive fits in an agent workflow
Google Drive is a Codex plugin associated with productivity workflows. For Google Drive, the plugin layer sits one level above individual skills: they can package capabilities, integrations, MCP connections or supporting resources into one installable unit. For discovery, Google Drive is most relevant to google drive, google workspace, and docs. The Google Drive plugin page is useful when you are choosing an integration first and then deciding which bundled capability to use.
What to check before using Google Drive
Before enabling Google Drive, check the source-backed metadata below for authentication, version, license and included capabilities. This record is tied to plugins/google-drive; the Google Drive upstream manifest remains the authority for installation requirements and behavior. Artifiner uses the Google Drive page to make comparison easier, not to replace the vendor or repository documentation.