Google Ads

Let your agents read your Google Ads account — campaigns, ad groups, keywords, search terms and performance (clicks, impressions, cost, conversions) — with GAQL queries through a Google service account. Read-only.

Connection

Authentication: API key (Service account JSON key).

Google Cloud console → pick (or create) a project → APIs & Services → enable “Google Ads API” → open the Google Ads API page → Overview: request the “Explorer” access level for the project → IAM & Admin → Service accounts → Create service account (no role needed) → Keys → Add key → JSON. Then in Google Ads → Admin → Access and security → Users → + : the service account email (…@….iam.gserviceaccount.com) with the “Read only” access level, on each account your agent should read. Paste the whole content of the downloaded JSON file.See Google Ads’s documentation.

Read actions (2)

Action	Description
`list_accessible_customers`	List the Google Ads accounts (resourceNames like “customers/1234567890”) the service account can access directly — call it first to find the customerId the other actions take.
`search`	Run a read-only GAQL query on a Google Ads account (search cannot modify anything). GAQL looks like SQL: SELECT fields FROM a resource (campaign, ad_group, ad_group_ad, keyword_view, search_term_view, customer, customer_client…) WHERE conditions (e.g. segments.date DURING LAST_30_DAYS, campaign.status = ‘ENABLED’) ORDER BY … LIMIT n. Always add a LIMIT. Money fields are in micros: divide cost_micros by 1 000 000 to get the account currency. Rows come 10 000 per page: while the response has nextPageToken, call again with the same query and that pageToken. Examples: “SELECT campaign.name, metrics.clicks, metrics.impressions, metrics.cost_micros FROM campaign WHERE segments.date DURING LAST_30_DAYS ORDER BY metrics.cost_micros DESC LIMIT 20” ; “SELECT search_term_view.search_term, metrics.clicks, metrics.conversions FROM search_term_view WHERE segments.date DURING LAST_7_DAYS ORDER BY metrics.clicks DESC LIMIT 50”.

Write actions (0)

This connector is read-only — it exposes no write actions.

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.

Last reviewed against the provider API: October 2026.

Using integrations

Communication

Scheduling

Project management

Docs & design

Files & storage

CRM & sales

Customer support

HR & recruiting

Commerce & billing

Developer tools

Observability & analytics

AI & media

Connection

Read actions (2)

Write actions (0)

Permissions

​Connection

​Read actions (2)

​Write actions (0)

​Permissions

Connection

Read actions (2)

Write actions (0)

Permissions