← Back to Skills Marketplace
8539
Downloads
21
Stars
0
Active Installs
19
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. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Ads connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Ads action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Ads examples; they add no Google Ads capability - Google Ads is not an event source, a trigger cannot read Google Ads data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, be comfortable that this skill can operate on Google Ads business data and can help create persistent automations if you approve them. Use read-only queries first, confirm every write or connection, avoid third-party trigger destinations unless you explicitly trust the host, and prefer the CLI OAuth flow over raw API keys.
Capability Assessment
Credentials
Requested Bash/Read/Grep/Glob and network access fit a CLI-based Google Ads integration. The skill warns not to inspect credential stores or unrelated secrets and limits raw API-key handling to environments where the CLI cannot be installed.
Install Mechanism
Installation is via pinned Maton CLI paths (npm or Homebrew) and there are no executable files shipped in the artifact; raw HTTP and SDK use are documented as alternatives with credential-handling cautions.
Instruction Scope
The skill includes shared trigger references for other Maton event sources, including HubSpot, but both SKILL.md and the reference files say these do not widen Google Ads access and should only be used when the user names that source.
Persistence & Privilege
OAuth tokens, functions, triggers, destinations, and event watches can create ongoing access or automation, but these are explicitly disclosed, user-approved, and accompanied by warnings about persistent forwarding, local execution, and deletion/cleanup.
Purpose & Capability
The skill's main purpose is Google Ads access through Maton OAuth, with read/list defaults and documented write operations for campaigns and related Google Ads resources. Hosted functions, triggers, and destinations are explained as optional automation mechanisms rather than hidden Google Ads capability.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install google-ads-api - After installation, invoke the skill by name or use
/google-ads-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.8
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.7
- Removed the sample skill-card.md file from the repository.
- No functional or API changes; documentation and usage remain the same.
v1.2.6
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.5
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.4
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.3
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
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
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. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Ads connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Ads action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Ads examples; they add no Google Ads capability - Google Ads is not an event source, a trigger cannot read Google Ads data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 8539 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.8.
More Skills