How to connect Google Slides to OpenClaw

The ClawHub skill teaches OpenClaw about Google Slides, but the calls run through the ClawLink plugin and your connected account. Make sure Google Slides 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 Slides from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Slides 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 Slides 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 cause is almost always Drive rather than Slides, because access to a presentation is a Drive permission. Check these in order. First, sharing: the connected Google account must have access to that specific file, and being able to open it in your browser proves nothing if the browser is signed in as a different account. Note that no Slides tool can fix this — sharing is changed in Drive or in the Google Slides UI, not through the API. Second, which account is connected, since personal and work accounts see completely different file sets. Third, a partial approval on the consent screen, which leaves a connection that reads but cannot write; reconnect and accept the full set. Fourth and least likely: a placeholder presentation id copied from documentation, which Google rejects as a permission error rather than a not-found, so have the agent look the deck up rather than accept an id from a prompt.

Ask the agent to diagnose it:

Tell me which Google account this connection is acting as, then try googleslides_presentations_get on the presentation id and quote the exact error. Do not retry it after that.

It exists, and it belongs to the connected account. Two things make it feel missing. The first is the account, again: if the agent is connected to a different Google identity than the one you are browsing Drive with, the deck is in that account's Drive and invisible in yours. The second is location — a newly created presentation lands in the root of My Drive rather than in whatever folder you had in mind, because folder placement is a Drive operation. Ask the agent for the presentation id or URL when it creates something, which removes the search entirely.

Ask the agent to diagnose it:

Give me the presentation id and the full URL of the deck you created, and tell me which Google account owns it.

Usually a sign the wrong tool is being used for the job. googleslides_presentations_batch_update applies low-level requests against specific object ids, so an agent constructing a deck through it has to get positioning, sizing, and text-range indexes right on every call, and small mistakes compound into a mangled slide. For generating content, googleslides_create_slides_markdown is far more reliable because the layout is handled for you. For matching an existing look, copy from a template and edit the copy. Reserve batch update for surgical changes where you know the object id you are targeting.

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

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Slides skill from ClawHub, then you click Connect in the dashboard to authorize Google Slides. 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 Slides 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 Slides working from chat.

No. That is the DIY path, and its real cost is not the setup but the maintenance: an app left in testing status issues refresh tokens that expire after seven days, so a hand-rolled Slides agent characteristically works for a week and then stops. ClawLink connects through an already-registered app, so you approve on Google's own consent screen and there is no client secret, no credentials file on your machine, and nothing about Slides in a config file.

Yes, and there are two quite different ways to do it. googleslides_create_slides_markdown builds slides from structured markdown, which is the reliable route when the agent is generating content — you describe the deck and it lays it out. googleslides_presentations_copy_from_template starts from an existing presentation, which is what you want when the deck has to match a house style. Building slide by slide through batch update is possible but is where formatting drifts, so prefer one of the first two unless you are making a targeted edit.

Not through these tools. Sharing, permissions, and access requests live in Google Drive, not in the Slides API, so the agent can create and edit a deck and still be unable to give anyone else access to it. If sharing is part of the workflow, connect Google Drive as well and let the agent handle the file's permissions there, or share it yourself once the deck is built. This is the distinction behind most "the agent made it but nobody can see it" reports.

Yes, if the connected account can open it. googleslides_presentations_get returns the presentation structure and googleslides_presentations_pages_get returns individual slides, which is what you want when the agent needs to summarize or audit a deck rather than change it. googleslides_get_page_thumbnail2 renders a slide as an image, which is useful when you want to check what something actually looks like rather than reasoning about its structure.

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