# How to connect Google Forms to OpenClaw (no API keys)

> Connect Google Forms to OpenClaw with ClawLink in one click — 10 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/openclaw/google-forms

The usual route to Google Forms access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Google Forms setup: install one ClawHub skill, connect Google Forms in the browser, and OpenClaw can call real Google Forms actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

**Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/google-forms

## Setup

It takes three steps to connect OpenClaw to Google Forms.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Google Forms** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect google-forms  # connect Google Forms (browser OAuth)
npx -y @useclawlink/cli actions google-forms  # list available actions
npx -y @useclawlink/cli run google-forms <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

```bash
openclaw plugins install clawhub:clawlink-plugin
```

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Google Forms in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys.

Verify the connection by asking OpenClaw:

> Create a Google Form called "\<title>" with googleforms_create_form, then use googleforms_batch_update_form to add the questions I listed above with the right types. Give me the form's edit and response links.

### Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Google Forms is connected in the dashboard, that agent calls the same 10 Google Forms tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Google Forms MCP for OpenClaw

Looking for a Google Forms MCP server for OpenClaw? ClawLink connects Google Forms to OpenClaw and exposes 10 Google Forms tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Google Forms integration](https://claw-link.dev/hermes/google-forms) works the same way.

Most guides to Google Forms and agents skip the form entirely and automate the response spreadsheet instead — export to Sheets, watch a column, act on rows. That works, and it is a different thing from what this does. Connecting Google Forms here gives OpenClaw the Forms API itself: it can build a form, change its questions, read structured responses, and register a watch that fires when new ones arrive. Setup is one browser sign-in with no Google Cloud project, no OAuth consent screen of your own, and no `token.json` on the machine running the agent.

## What the OpenClaw Google Forms integration can do

10 Google Forms tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10.

### 9 of 10 Google Forms tools for OpenClaw

| Tool | What it does |
|---|---|
| **Batch update form** `googleforms_batch_update_form` | Apply batch updates to a Google Form |
| **Create form** `googleforms_create_form` | Create a new Google Form |
| **Create watch** `googleforms_create_watch` | Create a watch to receive push notifications for form events |
| **Get form** `googleforms_get_form` | Get the structure and metadata of a Google Form |
| **Get response** `googleforms_get_response` | Get a single form response by ID |
| **List responses** `googleforms_list_responses` | List all responses submitted to a Google Form |
| **List watches** `googleforms_list_watches` | List all watches for a Google Form |
| **Set publish settings** `googleforms_set_publish_settings` | Update the publishing settings of a Google Form |
| **Renew watch** `googleforms_renew_watch` | Renews a watch on a Google Form, extending its expiration by one week from the time of renewal |

## Example prompts

**Build a form from a description**

> Create a Google Form called "\<title>" with googleforms_create_form, then use googleforms_batch_update_form to add the questions I listed above with the right types. Give me the form's edit and response links.

**Summarize what people said**

> Read the responses to form \<form id> with googleforms_list_responses and summarise the answers question by question, calling out anything that came up more than twice.

**Watch for new submissions**

> Register a watch on form \<form id> for new responses with googleforms_create_watch, then tell me when it expires and what I need to do to keep it alive.

**Close a form**

> Use googleforms_set_publish_settings to stop accepting responses on form \<form id>, then confirm the current state by reading it back with googleforms_get_form.

## How the Google Forms tools behave

A small toolset where the sequencing matters more than the arguments.

- **Creating a form and filling it are two calls.** `googleforms_create_form` makes an effectively empty form; `googleforms_batch_update_form` adds and edits the items. An agent that expects one call to do both reports success on an empty form.
- **Responses read better here than in a spreadsheet.** `googleforms_list_responses` and `googleforms_get_response` keep the link between question and answer, which a flattened sheet row loses.
- **Watches expire and must be renewed.** `googleforms_create_watch` starts one, `googleforms_list_watches` shows what exists, `googleforms_renew_watch` extends it. Nothing errors when one lapses — it simply stops.
- **Publish settings control whether the form accepts answers.** `googleforms_set_publish_settings` is how a form is opened or closed, rather than deleting or unsharing it.
- **Form ids are not the same as response-link ids.** Use the id the API returns, not one pulled from a public URL.

## ClawLink vs. building it yourself

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

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a Google Forms app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Forms through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Forms. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Google Forms actions to the runtime in a format your agent can reliably use. | 10 tools for Google Forms are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Google Forms to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Google Forms in the browser, and the 10 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Google Forms skill but can't call the tools
The ClawHub skill teaches OpenClaw about Google Forms, but the calls run through the ClawLink plugin and your connected account. Make sure Google Forms 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.

### Connection succeeds but no tools appear
Reconnect Google Forms from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Google Forms tools
Google Forms 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 Forms 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.

### Google Forms returns 403 or "permission denied" on one action while others work
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.

### Google Forms returns 403 "The caller does not have permission"
Search results answer this with three self-hosted fixes — add the Forms scope to your OAuth client, publish your consent screen out of testing, delete the stale token.json and re-authenticate. None of those apply here, because there is no OAuth client of yours, no consent screen you own, and no token file on your machine. The causes that do apply are simpler. First, access: the connected Google account must have edit access to that specific form, and opening it in a browser signed in as a different account proves nothing. Second, which account approved the connection, since personal and work accounts see entirely different forms. Third, a partial approval on the consent screen, which leaves a connection that reads but cannot write — reconnect from the dashboard and accept the full set. Fourth, a placeholder form id from an example, which Google rejects as a permission error rather than a not-found.

Ask the agent to diagnose it:

```text
Tell me which Google account this connection is acting as, then run googleforms_get_form on the form id and quote the exact error. Do not retry after that.
```

### Responses come back empty although the form has submissions
Two causes worth separating. The first is access level: reading responses needs more than being able to view the form, so an account with view-only access can fetch the form structure and get nothing back for responses. The second is the form id itself — the id in a form's edit URL and the id in its public response link are not interchangeable, and using the wrong one produces an empty or failing read that looks like there are no submissions. Have the agent fetch the form with googleforms_get_form first and confirm it is looking at the form you mean before you conclude anything about the responses.

Ask the agent to diagnose it:

```text
Run googleforms_get_form for the id I gave you and tell me the form's title and how many items it has. Then run googleforms_list_responses and tell me exactly what came back.
```

### The watch stopped firing for new responses
Watches expire, which is by design rather than a failure. googleforms_create_watch registers a notification with a limited lifetime, so a workflow that depends on it needs googleforms_renew_watch on a schedule or it goes quiet without any error appearing anywhere. Run googleforms_list_watches to see what is currently registered and when it lapses. If the workflow only needs to catch up rather than react instantly, reading responses periodically with googleforms_list_responses is simpler and has nothing to expire.

### OAuth finished in the browser but the account is still missing
Try reconnecting Google Forms and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a OpenClaw Google Forms integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Google Forms: link your Google Forms account once in the browser and OpenClaw can call the Google Forms API through 10 ready-made tools — no custom code or token handling.

### How do I add Google Forms to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Google Forms skill from ClawHub, then you click Connect in the dashboard to authorize Google Forms. OpenClaw calls the tools from the next message — no config files or API keys to manage.

### How long does it take to connect Google Forms to OpenClaw?
About two minutes. Sign in, click Connect next to Google Forms in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Google Forms up myself?
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 Forms working from chat.

### Do I need a Google Cloud project or a token file?
No, and this is the difference from every walkthrough you will find. Those have you create a project, enable the Forms API, configure an OAuth consent screen, run a local auth flow, and end up with a token.json sitting next to your script that expires and has to be regenerated — which is why so much of the troubleshooting advice online is "delete token.json and re-authenticate". There is no token file here and no consent screen of yours to publish. You approve access on Google's screen and the credential stays on the ClawLink server.

### Can the agent create a form, or only read responses?
Both. googleforms_create_form makes a new form and googleforms_batch_update_form changes its structure — adding questions, editing them, reordering, and updating settings. Reading is googleforms_list_responses for everything and googleforms_get_response for one submission. The practical note on creation is that a new form starts effectively empty, so building a real form is a create followed by a batch update that adds the items, rather than one call that does everything.

### How does the agent know when someone responds?
Through a watch. googleforms_create_watch registers a notification for new responses or schema changes, googleforms_list_watches shows what is registered, and googleforms_renew_watch keeps it alive — watches expire, so a watch created and forgotten stops firing after its window. This is the piece the spreadsheet-based approach replaces with polling a sheet, and it is more direct, but it does need renewing rather than being set once.

### Should I automate the form or the response spreadsheet?
It depends on where the work is. If the job is reading submissions and doing something with them, the linked spreadsheet is a perfectly good surface and the Google Sheets integration handles it, which is what most published workflows do. Use the Forms API when the form itself is part of the work: generating forms from a template, changing questions in response to something, publishing or unpublishing, or reading responses with their question structure intact rather than flattened into columns. The structured read is the underrated part, because a spreadsheet row loses which question an answer belonged to.

### OpenClaw installed the Google Forms skill but can't call the tools
The ClawHub skill teaches OpenClaw about Google Forms, but the calls run through the ClawLink plugin and your connected account. Make sure Google Forms 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.

## Related

- [Google Super](https://claw-link.dev/openclaw/google-super) — Unified access to multiple Google services in one integration
- [OpenClaw Google Drive integration](https://claw-link.dev/openclaw/google-drive) — Upload, search, and manage files
- [Google Analytics tools](https://claw-link.dev/openclaw/google-analytics) — Connect Google Analytics properties through hosted Google OAuth