List campaigns, run GAQL queries, and report performance — plus manage real ad spend by updating budgets, statuses, and bid ceilings. Write actions carry a per-mutation cost, so the integration spend cap bites. Runs through the Nango proxy.
| Category | 📣 Marketing |
| Connection | ⚡ OAuth 2.0 one-click, handled by Nango |
| Actions | 6 total — 3 read, 3 write |
Once connected, Google Ads exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.
| Action | Type | What it does | Proxy |
|---|---|---|---|
List Campaignslist-campaigns | Read | List campaigns in a Google Ads account via GAQL. | Yes |
Search (GAQL)search | Read | Run an arbitrary Google Ads Query Language query. | Yes |
Get Campaign Performanceget-campaign-performance | Read | Fetch per-campaign metrics over a date range. | Yes |
Update Campaign Budgetupdate-campaign-budget | Write | Set the daily amount on a campaign budget. Changes real ad spend. | Yes |
Set Campaign Statusset-campaign-status | Write | Enable, pause, or remove a campaign. | Yes |
Update Campaign Bid Ceilingupdate-campaign-bid | Write | Set the campaign-level manual-CPC bid ceiling. | Yes |
Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.
Google Ads is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration — it never means unlimited. See the Integrations overview for the full governance model.