# How to connect Google Tag Manager to OpenClaw (no API keys) > Connect Google Tag Manager to OpenClaw with ClawLink in one click — 15 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/google-tag-manager The usual route to Google Tag Manager access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Google Tag Manager setup: install one ClawHub skill, connect Google Tag Manager in the browser, and OpenClaw can call real Google Tag Manager actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/google-tag-manager ## Setup It takes three steps to connect OpenClaw to Google Tag Manager. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Google Tag Manager** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-tag-manager # connect Google Tag Manager (browser OAuth) npx -y @useclawlink/cli actions google-tag-manager # list available actions npx -y @useclawlink/cli run google-tag-manager --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Google Tag Manager in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Google Tag Manager to googletagmanager account read and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Tag Manager is connected in the dashboard, that agent calls the same 15 Google Tag Manager tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Tag Manager MCP for OpenClaw Looking for a Google Tag Manager MCP server for OpenClaw? ClawLink connects Google Tag Manager to OpenClaw and exposes 15 Google Tag Manager tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Google Tag Manager integration](https://claw-link.dev/hermes/google-tag-manager) works the same way. ## What the OpenClaw Google Tag Manager integration can do 15 Google Tag Manager tools are ready for OpenClaw once the account is connected. ### All 15 Google Tag Manager tools for OpenClaw | Tool | What it does | |---|---| | **Account read** `googletagmanager_account_read` | List GTM accounts or get one | | **Container read** `googletagmanager_container_read` | List or get containers | | **Workspace read** `googletagmanager_workspace_read` | List workspaces and their changes | | **Tag read** `googletagmanager_tag_read` | List or get tags | | **Trigger read** `googletagmanager_trigger_read` | List or get triggers | | **Variable read** `googletagmanager_variable_read` | List or get variables | | **Tag edit** `googletagmanager_tag_edit` | Create, update or revert a tag | | **Trigger edit** `googletagmanager_trigger_edit` | Create, update or revert a trigger | | **Variable edit** `googletagmanager_variable_edit` | Create, update or revert a variable | | **Built in variable read** `googletagmanager_built_in_variable_read` | List enabled built-in variables | | **Folder read** `googletagmanager_folder_read` | List folders and what is in them | | **Version read** `googletagmanager_version_read` | Get a version or the live one | | **Version header read** `googletagmanager_version_header_read` | List container versions | | **Workspace edit** `googletagmanager_workspace_edit` | Create, sync or preview a workspace | | **Version create** `googletagmanager_version_create` | Save workspace changes as a version | ## Example prompts **Googletagmanager Account Read** > Use Google Tag Manager to googletagmanager account read and walk me through the result in plain English. **Googletagmanager Container Read** > Use Google Tag Manager to googletagmanager container read and walk me through the result in plain English. **Googletagmanager Workspace Read** > Use Google Tag Manager to googletagmanager workspace read and walk me through the result in plain English. **Googletagmanager Tag Read** > Use Google Tag Manager to googletagmanager tag read and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Tag Manager working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Tag Manager app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Tag Manager through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Tag Manager. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Tag Manager actions to the runtime in a format your agent can reliably use. | 15 tools for Google Tag Manager are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Tag Manager to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Google Tag Manager in the browser, and the 15 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Google Tag Manager skill but can't call the tools The ClawHub skill teaches OpenClaw about Google Tag Manager, but the calls run through the ClawLink plugin and your connected account. Make sure Google Tag Manager is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Google Tag Manager from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Tag Manager tools Google Tag Manager tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Tag Manager call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Tag Manager returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Tag Manager and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Google Tag Manager integration? Yes. ClawLink is the fastest way to connect OpenClaw to Google Tag Manager: link your Google Tag Manager account once in the browser and OpenClaw can call the Google Tag Manager API through 15 ready-made tools — no custom code or token handling. ### How do I add Google Tag Manager to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Tag Manager skill from ClawHub, then you click Connect in the dashboard to authorize Google Tag Manager. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Google Tag Manager to OpenClaw? About two minutes. Sign in, click Connect next to Google Tag Manager in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Google Tag Manager up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Tag Manager working from chat. ### OpenClaw installed the Google Tag Manager skill but can't call the tools The ClawHub skill teaches OpenClaw about Google Tag Manager, but the calls run through the ClawLink plugin and your connected account. Make sure Google Tag Manager is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Connect Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences