# How to connect Google Super to Grok Bot (no API keys) > Connect Google Super to Grok Bot with ClawLink in one click — 404 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-super Grok Bot runs on its own cloud computer, so most Google Super guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Super setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Super 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-super` > 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 Super. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Super** — `npx -y @useclawlink/cli connect google-super`, 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-super # connect Google Super (browser OAuth) npx -y @useclawlink/cli actions google-super # list available actions npx -y @useclawlink/cli run google-super --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-super ``` 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 Super to googlesuper acl get 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 Super is connected in the dashboard, that agent calls the same 404 Google Super 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 Super MCP for Grok Bot Looking for a Google Super MCP server for Grok Bot? ClawLink connects Google Super to Grok Bot and exposes 404 Google Super 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 Super integration](https://claw-link.dev/openclaw/google-super) and the [Hermes Google Super integration](https://claw-link.dev/hermes/google-super) connect the same ClawLink account the same way. ## What the Grok Bot Google Super integration can do 404 Google Super tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 404. ### 30 of 404 Google Super tools for Grok Bot | Tool | What it does | |---|---| | **Acl get** `googlesuper_acl_get` | Retrieves a specific access control rule for a calendar | | **Acl list** `googlesuper_acl_list` | Retrieves the list of access control rules (ACLs) for a specified calendar, providing the | | **Aggregate column data** `googlesuper_aggregate_column_data` | Searches for rows where a specific column matches a value and performs mathematical operations | | **Autocomplete** `googlesuper_autocomplete` | Returns place and query predictions for text input | | **Batch get** `googlesuper_batch_get` | Retrieves data from specified cell ranges in a Google Spreadsheet | | **Batch get media items** `googlesuper_batch_get_media_items` | Returns the list of media items for the specified media item identifiers | | **Batch run pivot reports** `googlesuper_batch_run_pivot_reports` | Return multiple pivot reports in a batch for a GA4 property | | **Batch run reports** `googlesuper_batch_run_reports` | Return multiple analytics data reports in a batch | | **Calendar list get** `googlesuper_calendar_list_get` | Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar | | **Check compatibility** `googlesuper_check_compatibility` | List dimensions and metrics compatible with a GA4 report request | | **Colors get** `googlesuper_colors_get` | Returns the color definitions for calendars and events | | **Compute route matrix** `googlesuper_compute_route_matrix` | Calculates travel distance and duration matrix between multiple origins and destinations using | | **Create prompt post** `googlesuper_create_prompt_post` | Send a one-shot prompt to the Sanity Content Agent | | **Download file** `googlesuper_download_file` | Downloads a file from Google Drive by its ID | | **Download file operation** `googlesuper_download_file_operation` | Download file content using long-running operations | | **Events get** `googlesuper_events_get` | Retrieves a SINGLE event by its unique event_id (REQUIRED) | | **Events instances** `googlesuper_events_instances` | Returns instances of the specified recurring event | | **Events list** `googlesuper_events_list` | Returns events on the specified calendar | | **Events list all calendars** `googlesuper_events_list_all_calendars` | Return a unified event list across all calendars in the user's calendar list for a given time | | **Export document as PDF** `googlesuper_export_document_as_pdf` | Export a Google Docs file as PDF using the Google Drive API | | **Export google workspace file** `googlesuper_export_google_workspace_file` | Exports a Google Workspace document to the requested MIME type and returns exported file content | | **Fetch emails** `googlesuper_fetch_emails` | Fetches a list of email messages from a Gmail account, supporting filtering, pagination, and | | **Fetch message by message ID** `googlesuper_fetch_message_by_message_id` | Fetches a specific email message by its ID, provided the `message_id` exists and is accessible | | **Fetch message by thread ID** `googlesuper_fetch_message_by_thread_id` | Retrieves messages from a Gmail thread using its `thread_id`, where the thread must be | | **Find event** `googlesuper_find_event` | Finds events in a specified Google Calendar using text query, time ranges (event start/end | | **Find file** `googlesuper_find_file` | The comprehensive Google Drive search tool that handles all file and folder discovery needs | | **Find folder** `googlesuper_find_folder` | Find a folder in Google Drive by its name and optionally a parent folder | | **Find free slots** `googlesuper_find_free_slots` | Finds both free and busy time slots in Google Calendars for specified calendars within a | | **Generate IDS** `googlesuper_generate_ids` | Generates a set of file IDs which can be provided in create or copy requests | | **Geocode address with query** `googlesuper_geocode_address_with_query` | Map addresses to geographic coordinates with query parameter | ## Example prompts **Googlesuper Acl Get** > Use Google Super to googlesuper acl get and walk me through the result in plain English. **Googlesuper Acl List** > Use Google Super to googlesuper acl list and walk me through the result in plain English. **Googlesuper Aggregate Column Data** > Use Google Super to googlesuper aggregate column data and walk me through the result in plain English. **Googlesuper Autocomplete** > Use Google Super to googlesuper autocomplete 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 Super working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Super app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Super 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 Super. | 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 Super actions to the runtime in a format your agent can reliably use. | 404 tools for Google Super are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Super 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 Super in the browser, and the 404 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 Super 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 Super tools Google Super 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 Super 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 Super 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 Super 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 Super integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Super: link your Google Super account once in the browser and Grok Bot can call the Google Super API through 404 ready-made tools — no custom code or token handling. ### How do I connect Google Super 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-super` to authorize Google Super. 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 Super to Grok Bot? About two minutes. Sign in, click Connect next to Google Super in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Super 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 Super 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 Drive integration](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 - [Grok Bot Google BigQuery integration](https://claw-link.dev/grokbot/google-bigquery) — Query and manage datasets, tables, and jobs in Google BigQuery