Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Google Docs" |
| 4 | description: "Public support knowledge for Google Docs." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "googledocs" |
| 10 | --- |
| 11 | # Google Docs |
| 12 | |
| 13 | |
| 14 | ## `GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown and HTML tables |
| 15 | |
| 16 | `GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown. Markdown tables should work, and HTML tables can also be passed in the markdown payload when a table shape is needed. |
| 17 | |
| 18 | ## Google Docs tab-level read and edit is supported by specific Google Docs tools |
| 19 | |
| 20 | Google Docs tab-level access is supported. For reading tabs, use `GOOGLEDOCS_GET_DOCUMENT_BY_ID` or `GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT`. For editing specific tabs, use `GOOGLEDOCS_REPLACE_ALL_TEXT`, `GOOGLEDOCS_REPLACE_IMAGE`, or `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT`. |
| 21 | |
| 22 | ## Google Docs supports managed and customer-owned OAuth2 |
| 23 | |
| 24 | Use Composio-managed OAuth for the standard connection flow. Create a custom |
| 25 | auth config with the customer's Google OAuth app when they need control over |
| 26 | scopes, consent-screen branding, or Google Cloud project policy. A Composio |
| 27 | Project API key authenticates SDK/API calls to Composio; it is not a replacement |
| 28 | for the user's Google OAuth grant. |
| 29 | |
| 30 | ## Google sensitive scopes can cause app-blocked errors unless the OAuth app is verified |
| 31 | |
| 32 | Google may block OAuth consent when an app requests unverified sensitive scopes. For production Google Docs/Workspace usage with sensitive scopes, use a verified OAuth app and complete the required Google verification/CASA process where applicable. Without verification, users may see warnings or app-blocked errors. |
| 33 | |
| 34 | ## Google OAuth tokens are redacted from connected-account responses |
| 35 | |
| 36 | Provider tokens are redacted from connected-account API responses. Use Composio |
| 37 | tool execution or Proxy Execute instead of reading access or refresh tokens from |
| 38 | connected-account data. |
| 39 | |
| 40 | ## Multiple Google accounts require explicit multi-account selection |
| 41 | |
| 42 | Composio can keep multiple connected accounts for the same toolkit and user. Enable multi-account behavior for the session when needed, give each account a clear alias, and select the intended alias or connected-account ID during execution rather than relying on an implicit default. |
| 43 | |
| 44 | ## Tool Router v2 sessions require connected accounts to belong to the same user/entity |
| 45 | |
| 46 | Tool Router v2 sessions are scoped to a single `user_id`. Every connected account passed into that session must belong to the same entity, otherwise validation fails with `ToolRouterV2_InvalidConnectedAccountIds`. Reconnect the outlier Google account under the same `user_id` or create a separate session. |
| 47 | |
| 48 | ## Specify Google auth config IDs at session creation so Manage Connection uses the intended configs |
| 49 | |
| 50 | When creating a Composio session, pass `auth_configs` keyed by toolkit slug, such as `gmail`, `googledrive`, or `googlecalendar`. If specified, Manage Connection uses those auth configs directly instead of picking a default config. |
| 51 | |
| 52 | ## Platform connections are isolated from For You / Connect MCP connections |
| 53 | |
| 54 | Connections created on Platform (`dashboard.composio.dev`) are isolated from For You / Connect MCP and do not carry over. To use Google Docs/Sheets/Workspace through Connect MCP, ask the MCP server to connect the app from the client flow and complete that OAuth flow. |