# How to connect Google Ads to Grok Bot (no API keys) > Connect Google Ads to Grok Bot with ClawLink in one click — 10 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-ads Grok Bot runs on its own cloud computer, so most Google Ads guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Ads setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Ads 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-ads` > 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 Ads. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Ads** — `npx -y @useclawlink/cli connect google-ads`, 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-ads # connect Google Ads (browser OAuth) npx -y @useclawlink/cli actions google-ads # list available actions npx -y @useclawlink/cli run google-ads --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-ads ``` 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 Ads to googleads add or remove to customer list 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 Ads is connected in the dashboard, that agent calls the same 10 Google Ads 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 Ads MCP for Grok Bot Looking for a Google Ads MCP server for Grok Bot? ClawLink connects Google Ads to Grok Bot and exposes 10 Google Ads 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 Ads integration](https://claw-link.dev/openclaw/google-ads) and the [Hermes Google Ads integration](https://claw-link.dev/hermes/google-ads) connect the same ClawLink account the same way. ## What the Grok Bot Google Ads integration can do 10 Google Ads tools are ready for Grok Bot once the account is connected. ### All 10 Google Ads tools for Grok Bot | Tool | What it does | |---|---| | **Add or remove to customer list** `googleads_add_or_remove_to_customer_list` | Add or remove contacts from a Google Ads customer list | | **Create customer list** `googleads_create_customer_list` | Create a customer list in Google Ads | | **Get campaign by ID** `googleads_get_campaign_by_id` | Get a Google Ads campaign by ID | | **Get campaign by name** `googleads_get_campaign_by_name` | Get a Google Ads campaign by name | | **Get customer lists** `googleads_get_customer_lists` | Get customer lists in Google Ads | | **List accessible customers** `googleads_list_accessible_customers` | List Google Ads customers accessible to the account | | **Mutate ad group criteria** `googleads_mutate_ad_group_criteria` | Create, update, or remove keywords and other ad group criteria | | **Mutate ad groups** `googleads_mutate_ad_groups` | Create, update, or remove Google Ads ad groups | | **Mutate campaigns** `googleads_mutate_campaigns` | Create, update, or remove Google Ads campaigns | | **Search stream gaql** `googleads_search_stream_gaql` | Run a GAQL query stream in Google Ads | ## Example prompts **Googleads Add Or Remove To Customer List** > Use Google Ads to googleads add or remove to customer list and walk me through the result in plain English. **Googleads Create Customer List** > Use Google Ads to googleads create customer list and walk me through the result in plain English. **Googleads Get Campaign By Id** > Use Google Ads to googleads get campaign by id and walk me through the result in plain English. **Googleads Get Campaign By Name** > Use Google Ads to googleads get campaign by name 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 Ads working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Ads app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Ads 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 Ads. | 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 Ads actions to the runtime in a format your agent can reliably use. | 10 tools for Google Ads are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Ads 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 Ads in the browser, and the 10 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 Ads 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 Ads tools Google Ads 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 Ads 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 Ads 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 Ads 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 Ads integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Ads: link your Google Ads account once in the browser and Grok Bot can call the Google Ads API through 10 ready-made tools — no custom code or token handling. ### How do I connect Google Ads 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-ads` to authorize Google Ads. 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 Ads to Grok Bot? About two minutes. Sign in, click Connect next to Google Ads in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Ads 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 Ads 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 - [Google Super](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Grok Bot Google Drive integration](https://claw-link.dev/grokbot/google-drive) — Upload, search, and manage files - [Grok Bot Google Analytics integration](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth