Google Ads + OpenAI Dots

How to connect Google Ads to OpenAI Dots

Set up Google Ads for OpenAI Dots with Agent200, then check which tools are available to your agent.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Google Ads tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects Google Ads to OpenAI Dots through Agent200. When you finish, OpenAI Dots can call the Google Ads tools for each of your users.

Every call runs with that user's own Google Ads connection: Agent200 runs the OAuth flow, stores and refreshes the tokens, and executes the call. You do not build or maintain a Google Ads integration.

Connector
Google Ads
Works with
OpenAI Dots ยท Your own agent code
Authentication
Managed OAuth, per end user
Tools
6 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Google Ads enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Google Ads account. They approve access once, on Google Ads's own page.
  • A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

Connect Google Ads to OpenAI Dots

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Google Ads and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Set up the Agent200 SDK

    Add the SDK to your project and create a client with the key from the environment.

    agent.js
    Conceptual example
    Set 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,
    });
  3. 3

    Step 3: Let your user connect Google Ads

    Each end user authorizes their own Google Ads account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Google Ads's own page. Agent200 handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let 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);
    }
  4. 4

    Step 4: Run with the Google Ads tools

    Name the user, the model and Google Ads in the tools. The model decides when a Google Ads tool is needed, and Agent200 executes the call with the user's own connection.

    run.js
    Conceptual example
    Run 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);

Test your connection

Run one request to check everything is wired up.

Ask

Ask OpenAI Dots to list the Agent200 tools available for Google Ads, including which are read-only.

What should come back

  • A list of the Google Ads tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for Google Ads and make sure its tools are enabled. Tool availability depends on your project setup.

Get your API key

Create a key in the Agent200 dashboard. It reaches Google Ads and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Google Ads to OpenAI Dots.

Agent brief
Goal: connect Google Ads to OpenAI Dots with Agent200.
Guide: https://www.agent200.com/connectors/google-ads/framework/openai-dots/

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. Make sure Google Ads is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's Google Ads account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Google Ads.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "google_ads" in the tools. The model decides when a Google Ads tool is needed; Agent200 executes the call.
7. Check it works with this request: "Ask OpenAI Dots to list the Agent200 tools available for Google Ads, including which are read-only."
   What should come back:
   - A list of the Google Ads tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Google Ads, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /connectors/google-ads/framework/openai-dots.md

Google Ads tools OpenAI Dots can call

  • List accounts

    Read
    google_ads_list_accounts

    List the Google Ads accounts the user can access.

  • List campaigns

    Read
    google_ads_list_campaigns

    List the campaigns in an account and their status.

  • Run a report

    Read
    google_ads_get_report

    Get clicks, cost and conversions for campaigns, ad groups or keywords.

  • Update campaign status

    Write
    google_ads_update_campaign_status

    Pause or enable a campaign.

  • Update a budget

    Write
    google_ads_update_budget

    Change a campaign's daily budget.

  • Add a negative keyword

    Write
    google_ads_add_negative_keyword

    Add a negative keyword to a campaign.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input, the end user's id and the Google Ads tools.

  2. 02

    The model picks a tool

    The model decides whether a Google Ads tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It uses that user's own Google Ads connection, within the endpoints and scopes your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Google Ads account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Google Ads enforces what its API grants.

Troubleshooting

Why not connect Agent200 to a dot directly?

A dot uses the plugins connected to your ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. Building the agent with the Agent200 SDK, as on this page, is the route that works.

The request says Google Ads authorization is required

The end user has not connected Google Ads yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Google Ads's own page, then run the request again.

OpenAI Dots does not use the Google Ads tools

Check that Google Ads is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Google Ads in the request, or in the instructions, also helps the model choose the right tool.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows (services, endpoints and scopes), and Google Ads returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Google Ads again so they can approve the new access.

The results come from the wrong account

Every request names an end user (user_123 in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Google Ads connection, never another user's.

The API key was pasted into a chat or committed

Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

Use Google Ads with another framework

200 OK

Google Ads, connected to OpenAI Dots.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)