How to connect Google Analytics to Hermes Agent

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.

Reconnect Google Analytics from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Analytics 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 Analytics 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.

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.

This is the single most common Google Analytics failure in ClawLink: 21 of the 51 real tool errors we have logged. GA4 stores some dimension and metric combinations separately and refuses to query them together, so the pairing is rejected rather than returned empty. The useful part is that Google names the exact field to drop. Asking for the dimension campaignName with the metric screenPageViews returns Please remove screenPageViews to make the request compatible for example, and swapping the metrics returns Please remove campaignName instead. Attribution dimensions such as campaignName, campaignId and defaultChannelGroup are the usual culprits against page and user metrics. Tell your agent to remove the single field the error names and retry, rather than rebuilding the request from scratch. Ignore the hint about demographic dimensions that arrives with this error; it is generic text and it is usually pointing at the wrong cause.

The incompatibility error tells your agent to validate with google_analytics_check_compatibility, and then that tool fails with a 400 on the very combination you are trying to diagnose. It is not broken. Passing an already-incompatible pair makes it error instead of answering. Use it the other way round: send only the metrics you want plus compatibilityFilter: "INCOMPATIBLE", and it returns the full list of dimensions that will not work with them, each with its apiName and description. That is the call that actually tells you what to avoid, and the one to put in the prompt.

The agent used a Universal Analytics name or a GA4 interface label instead of an API name. The three differ, and the reporting interface never shows the API name. We have logged this with averageEngagementTime, averageUserEngagementDuration, sessionCampaign, sessionGoogleAdsKeywordText and exits, none of which exist in the Data API. Treat Google's suggestion with care, because it is often wrong: pageviews returns Did you mean keyEvents? when the field you actually want is screenPageViews, and exits returns Did you mean sessions? when GA4 simply has no exits metric. The reliable fix is to have the agent call google_analytics_get_metadata with properties/0/metadata first and choose apiName values from that response.

This one has no error string, because the call succeeds. A report with a valid property and a valid field list comes back with "rowCount": 0, an empty rows array, and the note Query returned no data for the specified parameters, and an agent reading that will tell you the site had no visitors. Three things produce it. The property genuinely has no data for that window, which is common on a property created for testing or one whose data stream was only just tagged. The date range landed outside the data, so ask for 30daysAgo to today before believing a quiet week. Or the report used a thresholded dimension: userAgeBracket, userGender, brandingInterest, audienceId and audienceName are withheld by Google when a report could identify individuals, and a low-traffic property returns nothing at all for them. Ask the agent to re-run with country or date before concluding the numbers are zero.

Two distinct causes that need opposite responses. If the tool was an administrative write, it needs Google's analytics.edit scope, which ClawLink does not request; seven of the 67 tools are in that group and reconnecting will never change it. If a report or a list tool fails this way, the grant itself is incomplete. ClawLink requests three Google scopes, which is the condition under which Google shows its granular consent screen with a separate checkbox per permission, and clearing the Analytics box produces exactly this error. Note that Google's Admin API accepts only analytics.readonly or analytics.edit, so the broader analytics permission on its own will read reports but still fail on google_analytics_list_account_summaries. Reconnect from the dashboard and leave every box on Google's consent screen ticked.

Despite the wording this is almost never a permissions problem, and reconnecting is the wrong first move. It is a property id the connected Google account cannot see, usually one the agent invented or copied out of documentation. Ask it to call google_analytics_list_account_summaries and reuse a property value from that response exactly as returned.

A hard Data API limit rather than a ClawLink one, and batch reports count each nested request on its own. Split the work into several calls of at most 9 dimensions and 10 metrics each, then join the results on a dimension they share, usually date. Asking one report to cover everything at once is the usual cause.

The report went out with no date range. Standard reports need at least one, for example dateRanges: [\{"startDate": "30daysAgo", "endDate": "today"\}]. The exception runs the other way: a cohort report carries its own window in cohortSpec and fails if you also pass dateRanges.

The Google grant behind the connection lapsed, usually because the Google password changed, the app was revoked under Third-party apps and services, or the account sat unused long enough for the refresh token to be invalidated. Nothing on the Hermes side fixes it. Reconnect Google Analytics from the ClawLink dashboard and approve the consent screen again, then start a fresh chat.

Try reconnecting Google Analytics and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to Google Analytics: link your Google Analytics account once in the browser and Hermes Agent can call the Google Analytics API through 67 ready-made tools — no custom code or token handling.

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 Analytics in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Google Analytics in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

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 Analytics working from chat.

No. That is the requirement every other route imposes, including Google's own Analytics MCP server, which asks you to create a Cloud project, enable the Analytics Data and Admin APIs by hand, create an OAuth client or an impersonable service account, run a gcloud login, add that service account's email to your GA4 property as a Viewer, and point a config file at a credentials JSON on disk. ClawLink owns the verified OAuth app instead. You pair Hermes once, click Connect, approve on Google's consent screen, and ClawLink holds and refreshes the token. There is no Cloud project, no OAuth client, no JSON key on the machine running Hermes, and no Property Access Management step for a robot account.

Three scopes: https://www.googleapis.com/auth/analytics.readonly, https://www.googleapis.com/auth/analytics and https://www.googleapis.com/auth/userinfo.profile. Because that is more than one non-sign-in scope, Google shows its granular consent screen with a checkbox per permission, and the connection only works if you leave them ticked. ClawLink does not request analytics.edit, so it cannot create, rename or archive properties, custom dimensions or custom metrics. You can review or revoke the grant at any time under Third-party apps and services in your Google account.

Not through ClawLink today. The 67 tools include GA4 Admin API endpoints that would edit a property, but they declare the analytics.edit scope ClawLink does not request, so they return 403. We confirmed this against a live connection rather than inferring it from the catalog. In practice this integration is reporting and inspection: standard, pivot, funnel and realtime reports, plus reads of property, audience, data stream, key event and link configuration, and field compatibility checks. If you need GA4 configuration writes, that is a real limit of this integration rather than something a reconnect will fix.

Google's server is open source, labelled experimental, described by Google as available for read requests only, and it runs locally over stdio, which means an always-on Hermes agent on a server or a phone cannot use it at all. Its README documents seven tools. Reaching a first query needs pipx, a Google Cloud project, two manually enabled APIs, an OAuth client or service account you create, and the gcloud CLI. ClawLink exposes 67 tools through a hosted connection with nothing to install or keep running, at the cost of routing calls through our infrastructure rather than your own machine. If you want a local, self-owned setup and are comfortable in the Google Cloud Console, the official server is a reasonable choice.

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.