Google Docs
On this page
Purpose
Google Docs runs actions from a Composio-connected Google account. Agent Core can use the enabled document tools, or a normal flow can run one selected action.
When to use it
- Read a document.
- Create or copy a document.
- Update document content after a reviewed flow step.
Required setup
- Create a Composio project API key in Composio Settings > Project Settings > API Keys. Add it in the component or select a saved Arkus Credential. Never put it in prompts, examples, or images.
- Use the component authorization flow to connect the Google Docs account. This provider grant is separate from the Composio key. The auth config chooses OAuth or API-key authentication and requested scopes. A workspace or organization administrator may need to approve permissions.
- When the connected account is active, Arkus loads available actions. Selected actions become separate Agent tools. The Google Docs toolkit page shows the catalog beyond this guide. Actions can vary by connected account and the toolkit version pinned by Arkus. Google Docs and Google Sheet are separate components with separate action sets. The examples below are not exhaustive.
- Missing actions? Check the Composio key, connected-account status, requested scopes, and administrator approval. Then reconnect or refresh.
How to use it
Tool Mode
- Add Google Docs, select the saved Composio Credential, and complete the account connection.
- Enable Tool Mode, keep only the Actions the Agent needs, and connect the tool output to Agent Core.
- Test the chosen action against a non-sensitive document.
Normal mode
- Choose one Action and provide its inputs.
- Connect the DataFrame output to the next step.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Composio API Key | Connects Arkus to Composio and loads the action schema. | Select a saved Credential. |
| Action | Chooses one available Docs action in normal mode. | Start with a read action. |
| Auth Mode | Appears when the connected toolkit requires an authentication choice. | Use the mode required by the authorized account. |
| Actions | Selects loaded actions that become separate Agent tools in Tool Mode. Builder can curate any relevant subset. Without a selection or component default, Arkus starts with the first five fetched actions. | Review the initial set and keep only the document actions the Agent needs. |
| Entity ID | Identifies the editor-side Composio user. Deployed flows use the authorized owner instead. | Leave default in normal Builder use. |
Expected result
Tool Mode gives Agent Core the enabled Docs tools. Normal mode returns a DataFrame. A deployed flow requires a saved owner Composio Credential and exactly one active owner account. If the account is missing, disabled, or ambiguous, Arkus asks the owner to reconnect before execution. Authorization failures during an action return a provider error.
Reference details
Auth Mode comes from the live Docs toolkit schema, not from the selected Action. Entity ID applies only in the Builder because deployments derive the owner. Complex action fields follow the selected action's schema. Review them before allowing an Agent to create or edit documents.
Works well with
Use Parser or Type Convert after a normal-mode response when the next step needs a specific field. In Tool Mode, give Agent Core only the document actions that fit the workflow.