Connect Google Drive

Solutioneer uses the Composio googledrive toolkit to read, export, and parse files in Google Drive during discovery. It is read-only — Solutioneer does not create or modify files through this toolkit.

Prerequisites

• A Composio API key in .env.
• A Google account with access to the Drive content you want Solutioneer to read.

What gets connected

The googledrive toolkit bundles read-only Drive access under one OAuth connection. After connecting, Solutioneer can call these specific tool slugs:

• GOOGLEDRIVE_FIND_FILE — search for a file by name or query.
• GOOGLEDRIVE_GET_FILE_METADATA — fetch metadata for a file.
• GOOGLEDRIVE_DOWNLOAD_FILE — download a non-Workspace file (for example, PDFs, images).
• GOOGLEDRIVE_EXPORT_GOOGLE_WORKSPACE_FILE — export a Google Doc, Sheet, or Slides file as markdown, CSV, or PDF.
• GOOGLEDRIVE_PARSE_FILE — parse a file into readable text.

All five are read-only. For writing Google Docs or Sheets, use the googlesuper toolkit.

How to connect

The normal flow runs inside Codex during an ingestion request:

1. Ask Solutioneer to pull from Google Drive. For example: “Ingest the discovery doc from my Drive into a fact sheet.”
2. Codex verifies that COMPOSIO_API_KEY is present.
3. Codex checks whether the googledrive toolkit is connected.
4. If it is not, Codex offers Connect now / Skip.
5. Connect now opens the Composio hosted login page in a browser tab.
6. You complete the Google OAuth flow and approve the Drive scopes.
7. Codex polls the connected account until it becomes ACTIVE.
8. Once active, Codex reads the requested files.

If browser tooling is unavailable, Codex provides the login link in chat and waits for you to finish the flow.

Connect from the Composio dashboard

If you prefer to connect ahead of time:

1. Open the Composio dashboard.
2. Go to Connections (or Toolkits).
3. Find the googledrive toolkit.
4. Click Connect and complete the Google OAuth flow for Drive.
5. Confirm the connection shows as Active.

Which skills read from Google Drive

• Discovery Context Ingester — the primary consumer. File contents are normalized into the fact sheet with composio://googledrive/... provenance markers.

Confirmation rules

Ingestion is triggered explicitly. Codex will not read from Drive unless you name a specific file or googledrive as a source. Once the toolkit is connected, subsequent ingestion runs do not re-prompt for consent.

Drive vs googlesuper

Two separate toolkits touch Google:

• googledrive (this page) is read-only. It finds, downloads, and parses files for discovery.
• googlesuper is write-capable. It creates Google Docs and Sheets when a skill is asked to publish an artifact. See Connect Google Docs & Sheets.

You can connect one, both, or neither. They do not depend on each other.

Troubleshooting

• File not found. Drive search is scoped to what the authenticated user can see. If the file is in a shared drive you do not have access to, ask for access or share the file directly.
• Export fails for Workspace files. Use GOOGLEDRIVE_EXPORT_GOOGLE_ WORKSPACE_FILE for native Google Docs, Sheets, and Slides. Codex picks this automatically when the target is a Workspace file.
• Connection stuck in pending. Re-open the Composio link and finish sign-in. Codex polls for up to five minutes before timing out.
• Wrong account. Each Google OAuth flow is tied to the account you sign in with. Disconnect the toolkit and reconnect with the right Workspace if needed.

See Troubleshooting for more.