If you run paid search, you have probably tried this already. You open ChatGPT Work, ask it to review last week's Google Ads account, and get a confident memo that was written from nothing. Work can write a crisp weekly memo, but it cannot see campaigns, search terms, or budgets unless another product reads the account. So you go looking for a plugin, and the results are connectors that dump spreadsheets into a chat. That is not what you wanted when you asked whether Work could pause a wasting term.
Google Ads plugins for ChatGPT Work do not exist as a first-party OpenAI app. US searchers look up "chatgpt plugins" about 1,300 times a month, and the Google Ads variants sit at 20 and 10 (DataForSEO Labs, US/English, 31 Oct 2026). OpenAI's help center lists Slack-class apps in its plugin directory and does not list Google Ads. Work launched on 9 July 2026. The pages that rank today are mostly ETL (extract, transform, load) connectors that pour reports into ChatGPT, which is reporting rather than campaign work. A paid media manager asking about Google Ads plugins for ChatGPT Work really wants to know whether Work can change the account. It can, through Metaflow, and only after you approve the write. The rest of this article shows how that loop runs, how to use it in a weekly review, and where connectors fit.
TL;DR
- There is no native Google Ads plugin in ChatGPT Work.
- Metaflow reads the connected account and queues the change.
- You approve spend. Never put bids on allow.
- ChatGPT Ads is OpenAI inventory. It is not your Google account.
- ETL connectors move reports. They do not run the account.
Why Google Ads plugins for ChatGPT Work do not ship from OpenAI
OpenAI packages the work apps most teams already live in, such as Gmail and Slack. It has not packaged the Google Ads API as a first-party plugin, and nothing in the help center suggests Work gets a special exception. Dots for Google Ads documented the same gap for standing agents, meaning scheduled assistants that rerun a job without you prompting them each time. Any product that reads or edits an account has to go through the Google Ads API with credentials someone controls. That is why the question of who holds the login matters more than which logo sits on a tile. In practice, Google Ads plugins for ChatGPT Work are a Metaflow install, not a settings toggle inside ChatGPT.
If a vendor says they "connected Google Ads to ChatGPT," ask one question: do they pull a report, or queue a mutation? A mutation is any change that writes to the account, such as adding a negative keyword or pausing a campaign. Most vendors pull a report. A paid media manager does not need ChatGPT to restate last week's CPA. They need a draft negative, a paused exact match, or a budget move they can accept or reject. If the answer to your question is a CSV, you have a connector and not an account workflow.
ChatGPT Ads is not your Google account
ChatGPT Ads is OpenAI's product for buying inventory inside ChatGPT. It has nothing to do with Google Ads plugins for ChatGPT Work, even though the names sound related. One sells attention inside the chat product. The other would, if it existed natively, touch your search account. It does not exist natively. Do not let a stakeholder conflate the two in a QBR, because the budget conversation, the reporting, and the permissions are entirely different. If someone asks you to "turn on ads in Work," find out which account they mean before anyone opens a login.
What Google Ads plugins for ChatGPT Work can do today
The setup is short. Install Metaflow, connect the Google Ads account in the Metaflow workspace, open Work, and describe the job in your own words. Metaflow starts the work and reads the account. Analysis steps never send or spend anything. Any write pauses and waits for your approval. That pause is the feature. It is what separates a reviewer you can trust from a model that edits a live account on a hunch.
The jobs below hold up well because each one produces a specific, checkable change:
- Search term harvest with suggested negatives (the search terms report shows the real queries that triggered your ads, and negatives block the wasteful ones)
- Budget moves between campaigns that already exist
- Pause or enable recommendations with the reason attached
- A weekly performance memo built from the performance snapshot
These jobs do not hold up, because the output cannot be verified or the scope is too wide:
- "Make ROAS 4 overnight"
- A new account build from a blank MCC (the manager account that sits above client accounts)
- Any mutation you have not read
The first list is made of bounded, auditable changes. The second asks the plugin to make strategic decisions it has no authority to make. Google Ads plugins for ChatGPT Work are a read-draft-approve loop. If you want policy-based changes while you sleep, that is a performance marketing agent, not a wider Work permission.
Read, draft, approve
This article calls that loop Read draft approve. The table shows who owns each step and what a finished step looks like. Use it as a checklist when you review a thread.
| Step | Who | What "done" looks like |
|---|---|---|
| Read | Metaflow | Campaigns, terms, budgets, and the snapshot date |
| Draft | Metaflow, shown in Work | A specific change with the reason |
| Approve | You | The write runs, or it dies in the queue |
| Refuse | You | The thread keeps the recommendation as a note |
The only step where money can move belongs to you. If the plugin asks you to approve and you are not looking at the account, reject it. Google Ads plugins for ChatGPT Work are not a substitute for looking.
The second table compares the main kinds of tools that claim a connection between Google Ads and ChatGPT.
| Connector class | Example | Good for | Bad for |
|---|---|---|---|
| ETL into chat | Windsor, Coupler | A chart in the thread | Pausing a term |
| Lookup | A keyword plugin | Query ideas | Account mutations |
| Engine | Metaflow | Read, draft, approve | Unattended spend |
Only the engine row can end with a change to the account, and even it stops at your approval. A paid media manager who installs only ETL will end up asking ChatGPT to restate last week's CPA. That is Chat work wearing a Work label. Google Ads plugins for ChatGPT Work only earn the name when a mutation can be queued and refused.
Client accounts make this sharper. Use one workspace per client. A shared MCC login inside a shared Work chat is how the wrong brand gets the negative. Put the account in Metaflow first, then open Work, then describe the week. If the plugin cannot see the account, it will invent a review from memory, and you should reject that review.
Brand safety sits next to spend. A drafted responsive search ad (RSA) that makes a claim you cannot prove is as dangerous as a bad bid. The approve step covers copy as well as money. If you only scan the budget number, you will ship the sentence.
These plugins also fail when the brief is "make it better." Name the cap, the wasted term pattern, and the one budget move you will consider. Specific jobs get specific drafts. Vague jobs get confident fluff.
When the book spans Google and Meta, do not merge the Work threads. Keep separate accounts and separate queues, with one plugin behind both. The sibling Meta page covers the other object model, and this page stays on search and Performance Max. If someone pastes a Meta export here, send them to the other URL.
Usage matters too. A weekly review that reruns the entire account history will burn through your Work usage allowance. Limit the window. Seven days is enough for the memo. Ninety days is a research job you should not run every Monday.
How to run a weekly Google Ads review in Work
Use one Work thread per account per week. That keeps the evidence, the drafts, and your decisions in one place, so you can find them later. Start with a prompt like this:
> Review the connected Google Ads account for last 7 days. List wasting search terms, campaigns over CPA cap, and one budget move you would make. Draft negatives and pauses. Do not write until I approve.
Let Metaflow finish before you react. Read the step field, which shows where the run is, so you can tell whether Google Ads plugins for ChatGPT Work returned a finished draft or a partial one. Approve line by line if the queue allows it. Then ask Work to write the memo for Slack. That memo is the artifact your team reads. The mutations are the side effect you chose.
If the same week includes SEO or outbound, Marketing plugins for ChatGPT Work is the hub. If someone on the team keeps doing this review in Chat, send them to ChatGPT Work vs Chat. Meta Ads plugins for ChatGPT Work is the sibling loop.
What you want from that memo is a short list a client can audit, not a tour of the account. Wasting terms should name the query, the campaign, the cost, and the reason it counts as waste. A pause should name the campaign and the CPA against the cap you put in the prompt. A budget move should name both campaigns and the amount, and it should still be a draft. If the memo says "performance was mixed" and then recommends a 20 percent bid increase, the review failed even if the sentences sound confident. Send it back. These plugins are doing the job when you can accept or reject each line without opening the UI to discover what the model meant.
The first week will feel slower than the Chat thread your team already has. That slowness is the point, because you are teaching the workspace which changes are in scope. The second week should reuse the same prompt, the same cap, and the same window, with only the dates changed. If every Monday starts from a blank chat, you do not have a review. You have a new opinion.
When Google Ads plugins for ChatGPT Work should refuse
Google Ads plugins for ChatGPT Work should refuse account-level experiments you have not scoped, changes in a client MCC you are not assigned to, and any "just raise bids 20 percent" instruction. The plugin is not a junior media buyer. It is a reader with a queue. When it refuses, that is the guardrail working, and you should treat the refusal as information and not as an error to prompt around.
Once the first review produces a memo you trust, a Dot can inherit the same plugin for the Monday rerun. A Dot is Metaflow's standing agent, which runs a saved job on a schedule. Design the first review in Work, then repeat it as a Dot. Do not let a Dot hold an allow-rule on spend, because a scheduled job with no human on the write is exactly the failure this loop exists to prevent.
Connectors versus the engine
Windsor.ai, Coupler, and similar tools rank for "chatgpt google ads plugin" because they move data into a chat. That is useful for a chart. It is not Google Ads plugins for ChatGPT Work in the sense a paid media manager means. If the output cannot pause a term, it is reporting.
Read, draft, approve is the only loop that deserves the name. A connector that lands yesterday's spend in a chat has done a reporting favor. It has not given you a change you can accept or reject. Windsor.ai and Coupler stay useful when the artifact is a chart for a meeting. They are the wrong install when the artifact is a negative, a pause, or a budget move between campaigns that already exist.
The weekly review should be boring enough to audit:
- Name the account, the date range, and the campaigns in scope before Work starts.
- Let the plugin read the connected account and draft the change with the reason beside it.
- Reject any draft that cannot name the campaign or the search term it wants to touch.
- Leave spend on approve. A good week is not a reason to widen the allow-rule.
Most teams meet this gap when a stakeholder says they already connected Google Ads to ChatGPT. Ask whether the connection can pause a term. If the answer is a CSV, you have a connector. Google Ads plugins for ChatGPT Work, in the sense that changes the account, means Metaflow reading the live account and waiting. The Dots guide for marketing shows how that same review becomes a standing Monday job once the first memo is one you trust. The content-led growth agent is a different desk, since it publishes pages and does not touch bids. The Dots plugins overview covers which tiles belong on the recurring job and which ones only answer a question.
Account-level experiments, an MCC you are not assigned to, and a casual instruction to raise bids are refusals, not edge cases. Put those refusals in the prompt so the draft comes back smaller. A plugin that returns twenty changes when you asked for one search-term harvest is not being thorough. It is making the approval meaningless. Keep one queue, one owner, and one week of data. That is the review a client can sit through without discovering a spend change they never saw.
The tension underneath all of this is accountability. When a model changes a bid, someone has to explain why, and a chat window that resets every Monday cannot do that. Most of the fear around this topic is really a fear of unexplained spend, which is reasonable.
That tension eases when the operator's judgment is written down once. The cap, the date window, and the definition of a wasting term become a reusable skill. The steps run in a workflow with an approval gate. An agent then keeps the same context from week to week. The work compounds instead of restarting, and discovery and execution live in one place. The review becomes a durable growth system rather than a conversation you re-explain every Monday.
Metaflow is where that handoff happens. You can explore a theory freely in Chat, then solidify what worked into skills, run it on a schedule with agents, and chain the steps in a flow that keeps a human on the write.
Frequently Asked Questions
Is there a Google Ads plugin for ChatGPT Work?
No, OpenAI does not ship a first-party Google Ads plugin for Work. What exists is a third-party route: Metaflow installs into Work, connects to your Google Ads account, reads it, and drafts changes for you to approve. If someone shows you an official Google tile in the plugin directory, read what it does. A tile that only returns reports is reporting, not a way to write to the account.
Can ChatGPT Work change my bids?
Yes, but only after a plugin queues the change and you approve it. Work does not hold your Google credentials, so on its own it can only talk about bids. With Metaflow connected, a bid or budget change appears as a draft with its reason, and the write runs only once you accept it. Keep bids on approve. A bid change that nobody read is the most expensive kind of error in this loop.
What is ChatGPT Ads versus Google Ads in Work?
They are unrelated products. ChatGPT Ads is OpenAI's inventory for placing ads inside ChatGPT, while Google Ads is the search and Performance Max account you already run. Work can only help with the Google account through a connected plugin. Say this plainly in the first client meeting. Metaflow only touches the Google side, so a request about buying placements inside ChatGPT is a separate conversation with a separate budget.
Can I connect Google Ads to ChatGPT without Metaflow?
Yes, you can connect it through a reporting connector such as Windsor.ai or Coupler, which pour account data into the chat. That works for a chart or a summary in a thread. It does not give you a draft negative or a pause that you can approve, because those tools do not queue writes. If you only need a number for a meeting, a connector is enough. If you need a term added as a negative, you need something that can draft the mutation and wait, which is the role Metaflow plays.
Should spend ever sit on allow?
No, keep spend on approve, including for scheduled Dots and after a strong quarter. An allow-rule lets a change run without a human reading it, and a single bad draft can burn budget before anyone notices. Overnight policy changes belong in a dedicated ads agent with its own limits and logs, which is the kind of setup Metaflow agents are meant for. Everything in Work should leave you the final say.
