← Back to Skills Marketplace
7578
Downloads
5
Stars
0
Active Installs
18
Versions
Install in OpenClaw
/install google-merchant
Description
Google Merchant Center API integration with managed OAuth. This is a write-capable integration — it can read, create, update, and delete products, inventories, data sources, promotions, account settings, and conversions in Google Shopping. Use this skill when users want to interact with their Merchant Center data. All write operations (creating/updating/deleting products, inventories, promotions, data sources, or account settings) require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. 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 Merchant Center connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Merchant Center 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 Merchant Center examples; they add no Google Merchant Center capability - Google Merchant Center is not an event source, a trigger cannot read Google Merchant Center 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
Install only if you intend to let an agent administer Google Merchant Center through Maton. Review every proposed write, webhook, trigger, hosted function, or raw API-key use carefully, confirm the exact account and resource IDs, and revoke unused connections or automations when the task is finished.
Capability Assessment
Credentials
Network access, OAuth login, and Maton CLI/API use are proportionate to the integration. The raw HTTP fallback requires a long-lived Maton API key, but the artifact limits it to environments without the CLI and gives clear handling guidance.
Install Mechanism
Installation is via a pinned Maton CLI release using npm or Homebrew, with optional pinned SDK packages; no embedded executable payloads or hidden install-time scripts were found in the inspected artifacts.
Instruction Scope
The skill is write-capable and includes automation, functions, triggers, and notification/webhook examples, but it repeatedly instructs agents to default to read/list calls and obtain explicit approval with specific resource identifiers before writes, connection creation, deployments, persistent forwarding, or local --exec automation.
Persistence & Privilege
OAuth credentials, hosted functions, triggers, destinations, and Merchant Center notification subscriptions can persist beyond a session, but the artifact discloses this and requires user confirmation, least-privilege scoping, and cleanup/revocation guidance.
Purpose & Capability
The purpose is coherent: manage Google Merchant Center products, inventory, data sources, reports, promotions, notifications, conversions, and account settings through Maton-authenticated API calls.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install google-merchant - After installation, invoke the skill by name or use
/google-merchant - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.7
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.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 file skill-card.md.
- No functional or documentation changes to the skill itself.
v1.0.7
- Clarified skill capabilities: This integration is now explicitly described as write-capable (can create, update, and delete Google Merchant resources).
- Added a warning in the authentication section to treat the Maton API key as a secret and instructions for secure key handling.
- Updated the description and usage guidance to emphasize that all write operations (create/update/delete) require explicit user approval with resource identifiers.
- No API or command-line changes; documentation and security guidance are improved.
v1.0.6
- Switched all API endpoints and connection management URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai.
- Updated documentation and code samples to use the new api.maton.ai base URL across all sections.
- Clarified connection management steps and responses for consistency with the new endpoint.
- Removed the LICENSE.txt file from the project.
v1.0.5
- Switched primary API version from v1beta to v1; all guides now reference the v1 endpoints.
- Added a new "Developer Registration" section, explaining required one-time GCP registration before using v1.
- Updated account ID discovery instructions and included fallback steps if v1beta is unavailable.
- Clarified API base URL and important usage notes.
- Removed v1beta examples and promoted v1 as the default throughout setup and API documentation.
v1.0.4
- Switched default and recommended API version from v1 to v1beta for all endpoints (v1 now requires GCP project registration).
- Updated API endpoint examples, including product listing and inventory, to use v1beta instead of v1.
- Added clear guidance and notes about v1 requiring GCP registration and v1beta being suitable for most integrations.
- Clarified product and inventory usage, including proper product ID format and restrictions for API data sources.
- Updated the Sub-API reference table and endpoint documentation for consistency with current Google Merchant API best practices.
v1.0.3
- Added a new clawdbot metadata section specifying required environment variable MATON_API_KEY.
- No changes to skill functionality or code. Documentation/metadata update only.
v1.0.2
- Documentation updated in SKILL.md; fixed incomplete section ending after "Search Reports".
- No functional or interface changes to the skill itself.
- The update clarifies and tidies documentation for end users.
v1.0.1
- Renamed the skill from `googlemerchant` to `google-merchant`.
- No changes were made to the skill's functionality or file content.
- Documentation and usage instructions remain unchanged.
v1.0.0
Initial release of the Google Merchant Center integration skill:
- Integrates Google Merchant Center API with managed OAuth, via Maton API key authentication.
- Allows management of products, inventories, data sources, promotions, and reports for Google Shopping through a unified API gateway.
- Provides detailed usage instructions and example code for listing, creating, and managing Merchant Center resources.
- Supports multiple OAuth connections, including methods to list, create, specify, and delete connections.
- Includes a modular sub-API structure to access core Merchant Center services (products, inventories, reports, etc.).
Metadata
Frequently Asked Questions
What is Google Merchant Center?
Google Merchant Center API integration with managed OAuth. This is a write-capable integration — it can read, create, update, and delete products, inventories, data sources, promotions, account settings, and conversions in Google Shopping. Use this skill when users want to interact with their Merchant Center data. All write operations (creating/updating/deleting products, inventories, promotions, data sources, or account settings) require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. 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 Merchant Center connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Merchant Center 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 Merchant Center examples; they add no Google Merchant Center capability - Google Merchant Center is not an event source, a trigger cannot read Google Merchant Center 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 7578 downloads so far.
How do I install Google Merchant Center?
Run "/install google-merchant" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Google Merchant Center free?
Yes, Google Merchant Center is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Google Merchant Center support?
Google Merchant Center is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Google Merchant Center?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.7.
More Skills