How to connect Google Tag Manager to Hermes Agent
Connect Google Tag Manager to Hermes with ClawLink in one click — 15 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
Read and edit tags, triggers and variables, and save container versions. Once connected, Hermes Agent can read and act on Google Tag Manager from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Google Tag Manager access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Google Tag Manager setup: pair once in the browser and your always-on Hermes agent can act on Google Tag Manager for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Google Tag Manager.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Google Tag Manager
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Google Tag Manager?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Google Tag Manager in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Google Tag Manager to googletagmanager account read and walk me through the result in plain English.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
Google Tag Manager MCP for Hermes
Looking for a Google Tag Manager MCP server for Hermes Agent? ClawLink connects Google Tag Manager to Hermes Agent and exposes 15 Google Tag Manager tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Google Tag Manager integration works the same way.
What the Hermes Agent Google Tag Manager integration can do
15 Google Tag Manager tools are ready for Hermes Agent once the account is connected.
All 15 Google Tag Manager tools for Hermes
| 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 |
Try it: find the Google Tag Manager tool you need
Browse the 15 Google Tag Manager tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Google Tag Manager to googletagmanager account read and walk me through the result in plain English.
Use Google Tag Manager to googletagmanager container read and walk me through the result in plain English.
Use Google Tag Manager to googletagmanager workspace read and walk me through the result in plain English.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Google Tag Manager
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Google Tag Manager integration?
Yes. ClawLink is the fastest way to connect Hermes to Google Tag Manager: link your Google Tag Manager account once in the browser and Hermes Agent can call the Google Tag Manager API through 15 ready-made tools — no custom code or token handling.
How do I connect Google Tag Manager to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Google Tag Manager in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Google Tag Manager to Hermes Agent?
About two minutes. Sign in, click Connect next to Google Tag Manager in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Tag Manager working from chat.
Hermes paired but still can't use Google Tag Manager
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
