← Back to Skills Marketplace
byungkyu

Google Ads

by byungkyu · GitHub ↗ · v1.2.2 · MIT-0
cross-platform ✓ Security Clean
7772
Downloads
21
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install google-ads-api
Description
Google Ads API integration with managed OAuth. Query campaigns, ad groups, keywords, and performance metrics with GAQL. Use this skill when users want to interact with Google Ads data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. The endpoints documented here are the intended surface, not a technical limit — the `maton api` passthrough can reach others the connection permits. Default to read and list calls, and confirm every write or new connection with the user.
Usage Guidance
Install only if you trust Maton and intend to let it access the selected Google Ads account. Prefer OAuth, use the narrowest account/scope available, verify the target connection before actions, and require a clear confirmation before any change that could affect spend, campaigns, ads, audiences, or reporting.
Capability Assessment
Credentials
The requested tools and network access are proportionate for a Google Ads API gateway skill, and no bundled scripts or hidden local execution were present.
Install Mechanism
Installation asks users to install Maton's CLI globally via npm or Homebrew, with optional SDK packages; this is disclosed and coherent with the integration purpose.
Instruction Scope
Runtime instructions emphasize read/list calls first, explicit user approval for connection creation and all modifying requests, target disambiguation for profiles/connections, and treating API-returned text as untrusted data.
Persistence & Privilege
OAuth tokens or API keys are stored by the Maton CLI in the OS credential store, with a raw HTTP fallback using MATON_API_KEY only when the CLI is unavailable; the artifact warns not to read, print, log, or persist secrets.
Purpose & Capability
The skill's purpose is Google Ads access for campaigns, keywords, reporting, and related API calls; it discloses that the Maton passthrough can reach any Google Ads endpoint allowed by the connected account, including high-impact write actions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install google-ads-api
  3. After installation, invoke the skill by name or use /google-ads-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.8
- Removed the sample file skill-card.md from the repository. - No other functional or documentation changes in this release.
v1.0.7
Version 1.0.7 - Update: CLI and API usage improvements, v24 upgrade - Updated examples and documentation to use Google Ads API v24 (was v23). - Enhanced quick start with CLI (`maton`) command examples for common queries. - Added installation and authentication instructions for the Maton CLI (with NPM and Homebrew). - Expanded code snippets for CLI, Python, and API workflows. - Clarified connection handling and how to specify connections in CLI and API calls.
v1.0.6
- Updated all endpoints from gateway.maton.ai and ctrl.maton.ai to new unified domain api.maton.ai. - Clarified that Maton proxies to Google, handles credentials, and write operations require explicit user approval. - Added a Security & Permissions section. - Minor text and code example refinements for improved clarity and consistency. - Removed LICENSE.txt file.
v1.0.5
- Added Clawdbot metadata to SKILL.md, including required environment variable details. - No functional or documentation changes to the skill's usage or interface.
v1.0.4
- Minor update to troubleshooting section for API key errors; now more concise and clearly titled "Troubleshooting: API Key Issues" - No functional or feature changes detected - Documentation and usage instructions remain unchanged
v1.0.3
- Quick start and all connection management examples now use Python one-liners instead of curl. - Added a "Troubleshooting: Invalid API Key" section with explicit steps for diagnosing API key errors. - No changes to the API itself or to existing code snippets for JavaScript and Python functions.
v1.0.2
- Added a note in the description recommending the use of the api-gateway skill for third party apps other than Google Ads. - Updated shell command examples to use environment variable syntax ($MATON_API_KEY). - Added important tips for using curl (-g for bracketed URLs, environment variable handling when piping). - Minor formatting and clarity improvements throughout the documentation.
v1.0.1
- Updated the base URL format to support direct mapping of native Google Ads API paths. - Added instructions for specifying which connection to use via the Maton-Connection header when managing multiple Google Ads connections. - Expanded example OAuth connection response to include metadata, creation_time, and last_updated_time fields. - Clarified that creating a Maton account is required to obtain an API key.
v1.0.0
- Major update: Transitioned to managed OAuth and API gateway for Google Ads. - Browser automation and Python SDK modes removed; now uses direct HTTP endpoints via Maton gateway. - Added instructions for API key-based authentication and Google Ads OAuth connection management. - Provided API reference for listing customers, running GAQL queries, and handling large result sets. - Included GAQL query samples and ready-to-use code examples for JavaScript and Python. - Streamlined troubleshooting, removed browser-specific details, and enhanced documentation links. - LICENSE.txt added; old reference markdown files removed.
Metadata
Slug google-ads-api
Version 1.2.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 13
Frequently Asked Questions

What is Google Ads?

Google Ads API integration with managed OAuth. Query campaigns, ad groups, keywords, and performance metrics with GAQL. Use this skill when users want to interact with Google Ads data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. The endpoints documented here are the intended surface, not a technical limit — the `maton api` passthrough can reach others the connection permits. Default to read and list calls, and confirm every write or new connection with the user. It is an AI Agent Skill for Claude Code / OpenClaw, with 7772 downloads so far.

How do I install Google Ads?

Run "/install google-ads-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Google Ads free?

Yes, Google Ads is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Google Ads support?

Google Ads is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Google Ads?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.2.

💬 Comments