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

Google Drive 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 Drive 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 about the OAuth grant, not the file, and the giveaway is the word scope. The connection's Google grant is missing the Drive permission ClawLink requests, either because the consent checkbox was unticked or because the grant predates the current permission set. In our logs it lands on googledrive_find_file and googledrive_find_folder first. Deleting a local token.json is the standard internet advice and there is no such file in a hosted flow; the actual fix is to reconnect Google Drive from the ClawLink dashboard and approve the Drive permission this time.

Hermes described a file by name where the tool needed its id. Have it run googledrive_find_file with a name contains query and reuse the id from the results, or paste the file's URL into chat, which carries the id inside it. This is the single most common Drive failure we log and the fix never varies.

The q expression or an orderBy value did not parse, and Google names no field in this error. Ask the agent to retry with only name contains '\<word>', verify results arrive, then add the mimeType or date conditions back one at a time. The broken clause identifies itself within a call or two.

A local file path reached the hosted runtime, which cannot read the machine Hermes runs on. Give the agent a public HTTPS link to the file, or paste the content and use googledrive_create_file_from_text. Uploads through this tool cap at 5 MB either way.

INITIALIZING means consent never completed; finish the OAuth flow in one browser session. REVOKED means the grant was withdrawn in the Google account afterwards. Either way, reconnect Google Drive from the ClawLink dashboard, approve the consent screen, and start a fresh chat so Hermes reloads the connection.

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

No. The Cloud project, the API you enable, the Desktop OAuth client, the client-secret JSON: that inventory exists so that someone owns a Google OAuth app, and with ClawLink that someone is us. You pair Hermes with the four commands above, click Connect, and approve on Google's own consent screen. Nothing gets created in a Cloud Console and nothing gets downloaded.

Yes, because API keys were never the mechanism for private data in the first place: Google scopes them to public information only. Every real Drive integration is OAuth underneath, and the differences are about who runs the OAuth app and where the token lives. Here ClawLink runs the app and holds the token, so the no-API-key promise in this page's title is a statement about architecture, not a workaround.

The grant is Google's full drive scope, read and write to what your account can see; 76 tools including upload, move and delete need exactly that, and pretending otherwise would be false comfort. We verified the scope string on a live connection. Your controls: Google's consent screen states the grant before it exists, sensitive operations pause for confirmation before running, revocation is immediate from Third-party apps and services in your Google account or by deleting the connection in the dashboard, and ClawLink deletes tool execution logs after 90 days. The strongest option remains connecting a Google account that only holds what the agent should touch.

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.