How to connect Google Drive to OpenClaw

The ClawHub skill teaches OpenClaw about Google Drive, but the calls run through the ClawLink plugin and your connected account. Make sure Google Drive 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.

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.

The word that matters in this error is scope, and it is about the OAuth grant behind your connection, not about who owns the file. ClawLink requests Google's Drive permission when you connect; a connection whose grant is missing it, because the Drive checkbox was left unticked on the consent screen or the connection predates the current permission set, fails exactly like this on googledrive_find_file and googledrive_find_folder while other integrations keep working. It is our second most common real Drive failure. Reconnect Google Drive from the dashboard and approve the Drive permission; sharing the file differently or retrying the call cannot fix a missing scope.

The agent described the file instead of identifying it. Drive tools take the opaque file id, which lives in the file's URL and in every googledrive_find_file result. Ask the agent to search first (name contains 'proposal') and reuse the id from the results verbatim. Sixty-two logged calls failed this way; none of them needed anything but the extra search step.

Google rejected the search expression and, unhelpfully, named no field. In our logs the cause is a malformed q (Drive's query syntax is strict about quoting and operators) or an unsupported orderBy value. Strip the query back to a single clause like name contains 'report', confirm it returns rows, then add mimeType or date conditions back one at a time until the broken clause shows itself.

The agent passed a path on its own machine, like /root/.openclaw/media/report.csv, and the hosted runtime has no way to read that disk. Three working routes: attach the file in chat so the plugin uploads the bytes (the npm plugin build reads local paths itself; the ClawHub build does not), host the file anywhere that serves plain HTTPS and pass that URL, or, for text content, skip files entirely with googledrive_create_file_from_text. Uploads also cap at 5 MB through this tool.

Two states, two stories. INITIALIZING means the OAuth flow never finished: the consent tab was closed early or approval happened in a different browser session; reconnect and complete the consent screen in one go. REVOKED means access was withdrawn in the Google account or by a workspace admin after the fact. Both end the same way: reconnect Google Drive from the ClawLink dashboard, approve, and start a fresh chat.

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 OpenClaw to Google Drive: link your Google Drive account once in the browser and OpenClaw can call the Google Drive API through 76 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Drive skill from ClawHub, then you click Connect in the dashboard to authorize Google Drive. OpenClaw calls the tools 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 OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Drive working from chat.

No. When the answer engines say the fix is to use a platform that already operates a verified Google OAuth app, so that you never create a Cloud project or download a credentials JSON, that is a description of this integration. ClawLink operates the app, you approve Google's consent screen, and the token never touches the machine running OpenClaw. The Cloud Console route still exists for people who want to own every part themselves; it is just not a prerequisite anymore.

Yes, and the reason is worth knowing: an API key could never do this job anyway. Google's API keys only authenticate access to public data, and your Drive is private, so real access always rides on OAuth. The keyless answers Google's results offer, Gemini inside Drive or an Apps Script bound to your account, stay inside Google's own products and give an OpenClaw agent nothing to call. Hosted OAuth is the route that ends in 76 callable tools with no key, no JSON, and nothing to rotate.

Plainly: the connection carries Google's full drive scope, read and write to the files your account can see, because that is what 76 tools including upload, move and delete require. We verified that scope string on a live connection, and Google's consent screen shows it to you before anything is granted. The controls are real, too. Sensitive operations like advanced copies stop and ask for confirmation before running. Revocation is immediate from your Google account's Third-party apps and services page or by deleting the connection in the dashboard. ClawLink deletes tool execution logs after 90 days. And the cleanest control costs nothing: connect a Google account that only contains what the agent should reach.

The ClawHub skill teaches OpenClaw about Google Drive, but the calls run through the ClawLink plugin and your connected account. Make sure Google Drive 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.