Skip to content

Connect Google Docs & Sheets

Solutioneer uses the Composio googlesuper toolkit for Google Docs and Google Sheets writeback. Every skill can write to googlesuper. Connect it once per Composio user and Codex can create docs and seed-data sheets on demand.

  • A Composio API key in .env.
  • A Google account that can create documents and sheets in the Workspace you want to write to.

The googlesuper toolkit bundles Google Docs and Google Sheets under one OAuth connection. After connecting, Solutioneer can call the following specific tool slugs:

  • GOOGLESUPER_CREATE_DOCUMENT_MARKDOWN — create a Google Doc from markdown.
  • GOOGLESUPER_CREATE_GOOGLE_SHEET1 — create a new Google Sheet.
  • GOOGLESUPER_ADD_SHEET — add a new tab to an existing Sheet.
  • GOOGLESUPER_CREATE_SPREADSHEET_ROW — append a row.

The normal flow runs inside Codex:

  1. Ask for an external write. For example: “Push this brief to a Google Doc in my Workspace.”
  2. Codex verifies that COMPOSIO_API_KEY is present.
  3. Codex checks whether the googlesuper 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.
  7. Codex polls the connected account until it becomes ACTIVE.
  8. Once active, Codex executes the write.

If browser tooling is unavailable (for example, in a sandboxed environment), Codex provides the login link in chat and waits for you to finish the flow.

If you prefer to connect ahead of time instead of during a run:

  1. Open the Composio dashboard.
  2. Go to Connections (or Toolkits, depending on the current layout).
  3. Find the googlesuper toolkit.
  4. Click Connect and complete the Google OAuth flow.
  5. Confirm the connection shows as Active.

Next time Codex checks for a googlesuper connection, it will find it already active.

Several skills can write to Google through googlesuper:

  • Account Intel Brief — pushes the brief as a Google Doc.
  • Demo Scenario Builder — pushes the demo script as a Google Doc and can seed a Google Sheet with demo data.
  • Integration Fit Gap Analyzer — pushes the fit-gap report as a Google Doc.
  • POC Handoff Orchestrator — pushes the POC plan and architecture note as Google Docs.

Codex always confirms before writing. You will see the destination and the toolkit status before the write executes. If you did not ask for a Google write, Solutioneer will not push to Google.

  • Connection stuck in pending. The most common cause is an incomplete OAuth flow. Re-open the 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. If you need a different Workspace, disconnect the toolkit in the Composio dashboard and reconnect with the right account.

See Troubleshooting for more.