How to connect Google Sheets 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 Sheets from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

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

The agent used the sheet's name where a tool needed its id, and both spellings of the message are real because the casing differs per tool. Paste the sheet's URL into the chat, or have the agent run googlesheets_search_spreadsheets with a name query and retry with the id it returns. This is the most common real Sheets failure we log, well ahead of anything Google-side.

The update tool refuses to guess between its two modes. USER_ENTERED parses input like typing, so dates and formulas come alive; RAW stores literal strings. Say which one you want in the prompt; USER_ENTERED is right for most real data. This omission accounts for 107 logged failures on its own.

The sheet title in the range does not exist in that spreadsheet, or the A1 reference is malformed. Titles are matched exactly and need single quotes when they contain spaces. Have Hermes call googlesheets_get_sheet_names and build the range from a returned title rather than assuming Sheet1.

If the error suggests alternatives, the agent invented a tool name and the suggestion (googlesheets_values_get for reads) is the fix. If Sheets tools are missing wholesale, the runtime's catalog is stale: reconnect from the dashboard and start a fresh chat. Ignore advice about deleting token.json or restarting a server process; a hosted connection has neither.

The Google grant behind the connection is missing its Drive permission. ClawLink asks for spreadsheets and Drive, each with its own checkbox on Google's consent screen, and a connection approved without the Drive box behaves exactly like this: reads by id succeed, search by name fails. Reconnect from the dashboard and leave every checkbox ticked.

Access was withdrawn on the Google side, by you under Third-party apps and services or by a workspace admin. Reconnect Google Sheets from the ClawLink dashboard and approve the consent screen again, then start a fresh chat so Hermes picks the connection up.

Try reconnecting Google Sheets 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 Sheets: link your Google Sheets account once in the browser and Hermes Agent can call the Google Sheets API through 40 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 Sheets 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 Sheets 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 Sheets working from chat.

No. The Cloud project, the two APIs you enable by hand, the Desktop OAuth client, the client-secret JSON: all of that is the price of the self-hosted route, and it is what most guides walk you through because they assume no one else can own the OAuth app. ClawLink owns a verified one. Pairing Hermes and clicking Connect is the entire setup, and no credential file ever lands on the machine running Hermes.

No. Sharing a sheet with a client_email is service-account advice, and there is no service account anywhere in this flow. The connection signs in as your Google account and sees what you see. When a call fails with a 403 despite a healthy connection, check the spreadsheet id the agent sent before touching any sharing settings; an invented or copied-from-an-example id is the usual culprit.

https://www.googleapis.com/auth/spreadsheets and https://www.googleapis.com/auth/drive, plus your email to label the connection, verified against a live connection rather than quoted from a catalog. Drive is in the list because searching spreadsheets by name or content is a Drive API operation. Each permission gets its own checkbox on Google's consent screen, and both need to stay ticked for every tool to work. Revoking is one click in your Google account's Third-party apps and services page or in the ClawLink dashboard.

Judge it by the mechanics rather than assurances. Google's consent screen lists exactly what is granted; the tool table on this page is the complete set of operations an agent can invoke; there is no API key or JSON file to leak because none exists. Revocation works instantly from your Google account or the dashboard, and ClawLink deletes tool execution logs after 90 days. The lever that matters most is yours: connect an account that only sees what the agent should, and lean on Sheets version history for anything write-heavy.

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.