Pause Google Ads Keywords with Zero Conversions, Previewed First

The pause-zero-conv-keywords workflow ships with PaidSync and finds enabled Google Ads keywords with at least 100 clicks, at least 20 in spend in the account's currency and zero conversions over the last 30 days. By default it previews: it returns the list and changes nothing. When you run it again with apply set to true, it pauses each keyword on the list and reports how many it paused and any errors. To run it, connect PaidSync to Claude or ChatGPT and ask it to preview the PaidSync pause-zero-conv-keywords workflow. A run counts as one task and works on every plan, including Free.

A paused keyword can be enabled again. The apply step needs a PaidSync sign-in, such as the Claude or ChatGPT connector, because a PaidSync API key cannot apply Google Ads changes. Like find-waste, it reads the 100 keywords with the highest cost in the window. Disclosure: PaidSync publishes this page.

What the pause workflow checks and does

The workflow is a few lines of code. This is all of it, in plain words.

If you name an account, it runs on that account. Otherwise it uses your active Google Ads account.
It reads the keyword performance report for the window.
It keeps each keyword that is enabled, has at least the minimum clicks and spend, and has exactly zero conversions.
With apply left at false, the default, it returns that list and stops. Nothing changes.
With apply set to true, it pauses each keyword on the list, one call per keyword with the confirmation flag set, and counts the ones that paused.

Settings you can change

Every setting is optional. Leave one out and the workflow uses the default below. Amounts are in the account's own currency.

Setting	Default	What it does
`account_id`	Your active account	The Google Ads account to check.
`lookback_days`	30	How many days back to read, up to 90.
`min_clicks`	100	A keyword needs at least this many clicks to count.
`min_spend`	20	A keyword needs at least this much spend to count.
`apply`	false	false previews the list. true pauses every keyword on it.

What it returns

What comes back depends on apply:

Preview (the default): mode "preview", candidate_count, and candidates, up to 100 keywords with their text, clicks and cost, plus a note on how to apply.
Applied: mode "applied", paused_count, attempted, and errors, the first 20 keywords that did not pause and why.

How to run it

In a chat. Connect PaidSync to Claude from Claude's connector directory, or to ChatGPT from its Plugins, connect Google Ads, then ask:

"Preview the PaidSync pause-zero-conv-keywords workflow on my Google Ads account. Do not apply it yet."

Claude calls paidsync_workflows_run with the workflow's name and your settings. Setup is in how to connect Google Ads to Claude.

From your own agent or code. Call the same tool on https://mcp.paidsync.ai/mcp:

// 1. Preview (changes nothing)
paidsync_workflows_run({
  name: "pause-zero-conv-keywords",
  params: { account_id: "123-456-7890" }
})

// 2. Pause the list, after you have read it
paidsync_workflows_run({
  name: "pause-zero-conv-keywords",
  params: { account_id: "123-456-7890", apply: true }
})

On a schedule. Schedule the preview, never the apply step. A Claude Code routine calls connector tools without asking during the run, so a scheduled apply would pause keywords with nobody looking. Run the preview on a timer and apply it in a chat.

Cost. A run counts as one PaidSync task, whatever it calls inside. The Free plan has 15 tasks a month with no credit card, and runs this workflow. Pro starts at $99 a month for 600 tasks.

Free for 15 tasks a month with no credit card, then priced by usage, from $99 a month for 600 tasks.

Start Free See a Demo

What keeps it from pausing the wrong thing

Preview by default. apply starts as false, so a run changes nothing until you set it to true yourself.
Enabled keywords with exactly zero conversions. A keyword with one conversion is left alone, whatever it cost.
The right account. A change aimed at a different account from the one the run is bound to is refused before the API call.
Your approval in Claude. Claude lets you set each connector tool to need your approval. Keep it on for paidsync_workflows_run, so you see apply set to true before the run starts.
Sign-in, not a key. A PaidSync API key cannot apply Google Ads changes, so an agent running on a key gets the preview and nothing more.

Limits to know

It reads the 100 keywords with the highest cost in the window, so zero-conversion keywords outside those 100 are not considered.
A run can call tools up to 100 times, and reading the report is one of them, so a list close to 100 keywords may not finish in one run. The ones left come back as errors, and a second run picks them up.
The preview shows each keyword's text, clicks and cost, not its ad group, so the same word in two ad groups appears twice.
A run stops after 60 seconds. If a long pause list runs past that, the run reports a failure, and the keywords it already paused stay paused, so check the account before you run it again.
The run with apply set to true reads the report again, so it can pause a slightly different list from the one the preview showed if the numbers changed in between.
If your conversions are often recorded days after the click, use a longer window before you pause.
Google Ads alone.

Other ways to do this job

Checked on 29 September 2026, on each option's own pages.

Google Ads automated rules. Google's examples include a "Pause keywords" rule on conditions such as conversions and cost per conversion, run daily, weekly, monthly or once, and Google says the "standard turnaround time for rules to run is within 2 hours after the conditions are triggered."
Google's own Google Ads MCP server. It cannot pause keywords. Google says it is strictly read-only.
One keyword at a time in a chat. PaidSync's pause_keyword pauses a single keyword and previews unless told to apply, and enable_keyword turns one back on.

What to do with the results

After you apply, check the paused keywords in a week or two. To turn one back on, ask Claude to enable it, which uses enable_keyword, or enable it in Google Ads. To stop the searches behind the waste as well, run negative-keyword-candidates.

Frequently asked questions

Does the workflow pause keywords straight away?

No. By default it previews and changes nothing. It pauses keywords only when you run it with apply set to true.

How do I undo a pause?

Enable the keyword again. In a chat, ask Claude to enable it, which uses PaidSync's enable_keyword tool, or turn it back on in Google Ads.

Why did it skip a keyword with no conversions?

It keeps enabled keywords with at least 100 clicks and 20 in spend by default, and it reads the 100 keywords with the highest cost in the window. A keyword below those thresholds, already paused, or outside those 100 is skipped.

Can I run it on a schedule?

Run the preview on a schedule and apply it in a chat. A Claude Code routine does not stop to ask before it calls a tool, so a scheduled apply would pause keywords with nobody reviewing the list.

Does it work with a PaidSync API key?

The preview does. Applying needs a PaidSync sign-in such as the Claude or ChatGPT connector, because an API key cannot apply Google Ads changes.

610+ tools. 14 platforms. One connection. Start free.

Get Started Free