CRM and sales
Google Ads for AI agents.
Managed auth, ready-made tools.
Report on campaigns, change campaign status and budgets, and add negative keywords in Google Ads on behalf of each of your users.
About Google Ads
With the Google Ads connector, your agent works in the Google Ads accounts each user can already manage. It can list campaigns, run performance reports, pause or enable a campaign, change a budget and add negative keywords, using only the tools your project allows.
Google Ads is Google’s advertising platform for search, display, YouTube and shopping ads.
Tools
What your agent can do in Google Ads.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Ads connection.
-
List accounts
Readgoogle_ads_list_accountsList the Google Ads accounts the user can access.
-
List campaigns
Readgoogle_ads_list_campaignsList the campaigns in an account and their status.
-
Run a report
Readgoogle_ads_get_reportGet clicks, cost and conversions for campaigns, ad groups or keywords.
-
Update campaign status
Writegoogle_ads_update_campaign_statusPause or enable a campaign.
-
Update a budget
Writegoogle_ads_update_budgetChange a campaign's daily budget.
-
Add a negative keyword
Writegoogle_ads_add_negative_keywordAdd a negative keyword to a campaign.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Google Ads, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read campaigns and reports, and switch off
google_ads_update_budgetso it can never change spend. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reports but not campaign changes. A call outside them is refused.
Get started
Connect Google Ads
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google Ads
Each end user authorizes their own Google Ads account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google Ads account, once. const connection = await agent200 .user("user_123") .connect("google_ads"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google Ads tools
Name the user, the model and the tools. The model decides which Google Ads tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Which campaigns spent the most last week", tools: ["google_ads"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Google's own sign-in page. You never see or store their Google password.
-
What access is requested
The scopes the connection needs, such as managing Google Ads campaigns, listed on Google's authorization screen. Users can remove the app later from their Google Account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Ads connector and how to use it.
Connector: Google Ads, through Agent200. In code: "google_ads". What it does: Report on campaigns, change campaign status and budgets, and add negative keywords in Google Ads on behalf of each of your users. Page: https://www.agent200.com/connectors/google-ads/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google Ads's own page, through the authorization link Agent200 returns. Never ask a user for a Google Ads password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_ads_list_accounts, google_ads_list_campaigns, google_ads_get_report. Write tools: google_ads_update_campaign_status, google_ads_update_budget, google_ads_add_negative_keyword. Name "google_ads" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/google-ads/framework/claude/ https://www.agent200.com/connectors/google-ads/framework/chatgpt/ https://www.agent200.com/connectors/google-ads/framework/claude-code/ https://www.agent200.com/connectors/google-ads/framework/muse/ https://www.agent200.com/connectors/google-ads/framework/grok-bot/ https://www.agent200.com/connectors/google-ads/framework/openai-dots/ https://www.agent200.com/connectors/google-ads/framework/claude-duet/ https://www.agent200.com/connectors/google-ads/framework/hermes-agent/ https://www.agent200.com/connectors/google-ads/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/google-ads.md
Guides
Use Google Ads with the AI you build on.
Step-by-step setup for Google Ads with a specific model, assistant or agent framework.
-
Google Ads + Claude
How to connect Google Ads to Claude
-
Google Ads + ChatGPT
How to connect Google Ads to ChatGPT
-
Google Ads + Claude Code
How to connect Google Ads to Claude Code
-
Google Ads + Muse
How to connect Google Ads to Muse
-
Google Ads + Grok Bot
How to connect Google Ads to Grok Bot
-
Google Ads + OpenAI Dots
How to connect Google Ads to OpenAI Dots
-
Google Ads + Claude Duet
How to connect Google Ads to Claude Duet
-
Google Ads + Hermes Agent
How to connect Google Ads to Hermes Agent
-
Google Ads + OpenClaw
How to connect Google Ads to OpenClaw
FAQ
Google Ads and Agent200, answered.
Who handles the Google Ads OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Ads.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Ads connection, never another user's. It cannot reach anything the user or Google Ads has not authorized.
Can I limit what my agent can do in Google Ads?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.