# How to connect Google Tasks to Grok Bot (no API keys) > Connect Google Tasks to Grok Bot with ClawLink in one click — 16 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/google-tasks Grok Bot runs on its own cloud computer, so most Google Tasks guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Tasks setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Tasks actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect google-tasks` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Google Tasks. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Tasks** — `npx -y @useclawlink/cli connect google-tasks`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-tasks # connect Google Tasks (browser OAuth) npx -y @useclawlink/cli actions google-tasks # list available actions npx -y @useclawlink/cli run google-tasks --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect google-tasks ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Google Tasks to googletasks batch execute and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Tasks is connected in the dashboard, that agent calls the same 16 Google Tasks tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Tasks MCP for Grok Bot Looking for a Google Tasks MCP server for Grok Bot? ClawLink connects Google Tasks to Grok Bot and exposes 16 Google Tasks tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Google Tasks integration](https://claw-link.dev/openclaw/google-tasks) and the [Hermes Google Tasks integration](https://claw-link.dev/hermes/google-tasks) connect the same ClawLink account the same way. ## What the Grok Bot Google Tasks integration can do 16 Google Tasks tools are ready for Grok Bot once the account is connected. The 14 below are the ones people reach for most; your agent can call all 16. ### 14 of 16 Google Tasks tools for Grok Bot | Tool | What it does | |---|---| | **Batch execute** `googletasks_batch_execute` | Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. | | **Clear tasks** `googletasks_clear_tasks` | Permanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone. | | **Create task list** `googletasks_create_task_list` | Creates a new task list with the specified title and returns a tasklist_id. Use the returned tasklist_id (not the title) when calling GOOGLETASKS_INSERT_TASK or other task operations. | | **Get task** `googletasks_get_task` | Retrieve a specific Google Task. REQUIRES both `tasklist_id` and `task_id`. Tasks cannot be retrieved by ID alone - you must always specify which task list contains the task. | | **Get task list** `googletasks_get_task_list` | Retrieves a specific task list from the user's Google Tasks if the `tasklist_id` exists for the authenticated user. | | **Insert task** `googletasks_insert_task` | Creates a new task in a given `tasklist_id`, optionally as a subtask of an existing `task_parent` or positioned after an existing `task_previous` sibling, where both `task_parent` and `task_previous` must belong to the same… | | **List all tasks** `googletasks_list_all_tasks` | Tool to list all tasks across all of the user's task lists with optional filters. Use when the agent needs to see all tasks without knowing which list to query first. | | **List task lists** `googletasks_list_task_lists` | Fetches the authenticated user's task lists from Google Tasks; results may be paginated. Response contains task lists under the `items` key. | | **List tasks** `googletasks_list_tasks` | Retrieves tasks from a Google Tasks list; all date/time strings must be RFC3339 UTC, and `showCompleted` must be true if `completedMin` or `completedMax` are specified. | | **Move task** `googletasks_move_task` | Moves the specified task to another position in the task list or to a different task list. | | **Patch task** `googletasks_patch_task` | Partially updates an existing task (identified by `task_id`) within a specific Google Task list | | **Patch task list** `googletasks_patch_task_list` | Updates the title of an existing Google Tasks task list | | **Update task full** `googletasks_update_task_full` | Fully replace an existing Google Task using PUT method | | **Update task list** `googletasks_update_task_list` | Updates the authenticated user's specified task list | ## Example prompts **Googletasks Batch Execute** > Use Google Tasks to googletasks batch execute and walk me through the result in plain English. **Googletasks Clear Tasks** > Use Google Tasks to googletasks clear tasks and walk me through the result in plain English. **Googletasks Create Task List** > Use Google Tasks to googletasks create task list and walk me through the result in plain English. **Googletasks Get Task** > Use Google Tasks to googletasks get task and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Tasks working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Tasks app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Tasks through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Tasks. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Tasks actions to the runtime in a format your agent can reliably use. | 16 tools for Google Tasks are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Tasks to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Tasks in the browser, and the 16 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Google Tasks from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Tasks tools Google Tasks tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Tasks call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Tasks returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Tasks and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Google Tasks integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Tasks: link your Google Tasks account once in the browser and Grok Bot can call the Google Tasks API through 16 ready-made tools — no custom code or token handling. ### How do I connect Google Tasks to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect google-tasks` to authorize Google Tasks. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Google Tasks to Grok Bot? About two minutes. Sign in, click Connect next to Google Tasks in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Tasks up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Tasks working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Grok Bot Google Super integration](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Google Drive tools](https://claw-link.dev/grokbot/google-drive) — Upload, search, and manage files - [Google Analytics](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth