# How to connect Google Forms to Hermes Agent (no API keys)

> Connect Google Forms to Hermes 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/hermes/google-forms

Most guides for giving Hermes Agent Google Forms access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Google Forms setup: pair once in the browser and your always-on Hermes agent can act on Google Forms for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

**Start here — paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

## Setup

It takes three steps to connect Hermes to Google Forms.

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

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then 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 Hermes:

> Create a Google Form titled "Team Lunch Survey" with googleforms_create_form (title in info.title), then use googleforms_batch_update_form to add three multiple-choice questions with the option list. Read the form back with googleforms_get_form to confirm the revisionId is current before the batch update.

### Using a different agent?

The Hermes 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 Hermes

Looking for a Google Forms MCP server for Hermes Agent? ClawLink connects Google Forms to Hermes Agent 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 OpenClaw instead? The [OpenClaw Google Forms integration](https://claw-link.dev/openclaw/google-forms) works the same way.

Google does not ship an official Google Forms MCP server: the Workspace MCP lineup is Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, and People, with Forms absent. So the search engine answers route Forms work through Form-to-Sheet pipelines in Zapier or Apps Script, or a community server that still needs your own Google Cloud OAuth app. ClawLink is the direct route: one browser consent screen, then the 10 Google Forms API tools below work from chat. Form responses come back with `googleforms_list_responses` instead of a spreadsheet round trip.

## The routes search engines teach for Google Forms, and how this page differs

Every one of them either needs a Cloud project or a spreadsheet in the middle.

- **Google Workspace MCP servers**: Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, People. Forms is not on the list, so there is no Google-managed MCP route to Forms at all.
- **Form -> Sheet -> webhook pipelines**: the architecture the AI Overview teaches for reading responses, usually built in Zapier or Apps Script. It copies submissions into a spreadsheet and then watches the sheet; `googleforms_list_responses` reads the source of truth directly.
- **Community Forms MCP servers and the Forms REST API**: they work, but they run under your own Google Cloud OAuth app or service account, which is the Cloud project setup this page removes.
- **ClawLink (this page)**: ten hosted tools, browser OAuth, no Cloud project for the six form tools, and a straight answer about the four that still need Pub/Sub.

Using OpenClaw as well? The [OpenClaw Google Forms integration](https://claw-link.dev/openclaw/google-forms) is the same hosted setup with the same ten tools.

## What the Hermes Agent Google Forms integration can do

10 Google Forms tools are ready for Hermes Agent 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 Hermes

| 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

**Create a form with questions**

> Create a Google Form titled "Team Lunch Survey" with googleforms_create_form (title in info.title), then use googleforms_batch_update_form to add three multiple-choice questions with the option list. Read the form back with googleforms_get_form to confirm the revisionId is current before the batch update.

**Read submissions directly**

> Use googleforms_list_responses on my feedback form id with a filter for timestamp > 2026-08-01T00:00:00Z, paginate with page_token, and summarize the last two weeks of answers.

**Publish or unpublish**

> Use googleforms_set_publish_settings on my quiz form id: set publishSettings.publishState to PUBLISHED so respondents can submit, and tell me the share link.

**Watch responses without Pub/Sub**

> I do not have a Google Cloud Pub/Sub topic. Instead of googleforms_create_watch, list the responses to my signup form every message and tell me when a new name appears.

## Google Forms tools and the Pub/Sub trap

Ten tools on this page. Four of them are unusable without a Google Cloud Pub/Sub topic, and two of the remaining six disagree on argument casing. All shapes below are read from the live schemas.

- **Four of the ten tools need a Cloud Pub/Sub topic, not just a form.** `googleforms_create_watch` requires a `target` object whose `topicName` is a fully qualified Cloud Pub/Sub name like `projects/my-project/topics/my-topic`, and `googleforms_list_watches`, `googleforms_renew_watch`, and `googleforms_delete_watch` all operate on those watches. A hosted OAuth connection grants Google Forms and Drive scopes, not Cloud Pub/Sub, so watch tool calls fail for the connected user's account unless that account also owns a Pub/Sub topic. The other six tools need no such setup.
- **Argument casing changes between tools.** `googleforms_get_form`, `googleforms_batch_update_form`, and `googleforms_create_watch` take camelCase `formId`, while `googleforms_list_responses`, `googleforms_set_publish_settings`, `googleforms_renew_watch`, and `googleforms_delete_watch` take snake_case `form_id`. An agent that copies the argument from one call to the next gets `arguments.formId is required` or `arguments.form_id is required` against the same integration.
- **`googleforms_create_form` needs only `info.title`.** The live schema marks the whole `info` object required, with `title` the one field inside it that is always required; `description` and `documentTitle` are optional. The tool creates an empty form: questions come later via `googleforms_batch_update_form`.
- **`googleforms_list_responses` paginates at 5,000.** `page_size` defaults to 5000 and `page_token` continues the page. A `filter` accepts timestamp expressions like `timestamp > 2026-08-01T00:00:00Z`. An agent that ignores pagination can silently miss responses past the first page.
- **`googleforms_batch_update_form` requires the current `writeControl.targetRevisionId` for safe edits.** The schema's writeControl takes a target revision id; using a stale one fails the batch with an edit conflict. The agent must read the form with `googleforms_get_form` to pick up the latest revisionId before applying changes.
- **The connection requests five scopes.** `forms.body`, `forms.body.readonly`, `forms.responses.readonly`, `drive`, `drive.file`, and `drive.readonly` from the live toolkit auth config. That is read/write on the connected user's forms and their Drive files, so the agent acts as the connected user; the grant is revocable at myaccount.google.com/permissions.

## 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 Hermes Agent. 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 Hermes Agent 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.

### Hermes paired but still can't use Google Forms
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`.

### 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.

### 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 Hermes Agent Google Forms integration?
Yes. ClawLink is the fastest way to connect Hermes to Google Forms: link your Google Forms account once in the browser and Hermes Agent can call the Google Forms API through 10 ready-made tools — no custom code or token handling.

### How do I connect Google Forms to Hermes with ClawLink?
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 Forms in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

### How long does it take to connect Google Forms to Hermes Agent?
About two minutes. Sign in, click Connect next to Google Forms in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. 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 to connect Google Forms to Hermes Agent?
Not with ClawLink, for the six form tools. The connection is a hosted OAuth grant with Google Forms and Drive scopes, so there is no Cloud project, no API key, and no OAuth app to register. The exception is the four watch tools: they push notifications through Cloud Pub/Sub and need a topic in a Google Cloud project, which a hosted OAuth grant does not include. Use `googleforms_list_responses` on a schedule instead of watches if you do not run a Cloud project.

### Is there an official Google Forms MCP server?
No. Google's Workspace MCP server lineup covers Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, and People, and Forms is not among them, as of the July 2026 configuration guide. Community MCP servers exist, but they run against the Forms REST API under your own OAuth app or service account. ClawLink's ten hosted tools are the direct route that skips the OAuth app entirely.

### How do I read form responses without building a Form-to-Sheet pipeline?
Call `googleforms_list_responses` with the form id. That is the direct forms.responses.list path, and it is what the search engines omit when they recommend routing submissions through a spreadsheet and a webhook. The tool returns responses with page_token pagination at 5,000 per page, and the same call can filter by timestamp. No Sheets copy, no Zapier step, no webhook.

### What can the agent actually do with my forms?
It acts as the connected Google account within five scopes: forms.body, forms.body.readonly, forms.responses.readonly, drive, drive.file, and drive.readonly. Concretely: create and edit forms, batch-update questions and sections, read and export responses, and manage publish settings. The four watch tools additionally need a Cloud Pub/Sub topic the connected account can reach. Everything the agent touches is a form or Drive file the connected account can already see.

### Why does Hermes say it cannot create a form watch?
Because watches are Pub/Sub subscriptions, not Forms features. `googleforms_create_watch` needs a fully qualified Cloud Pub/Sub topic name (`projects/\{project\}/topics/\{topic\}`) in the target argument, and the hosted connection does not grant Cloud Pub/Sub. If you have a Cloud project, create the topic there and pass its name; if you do not, poll with `googleforms_list_responses` instead, which needs nothing beyond the form id.

### Hermes paired but still can't use Google Forms
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`.

## Related

- [Connect Google Classroom](https://claw-link.dev/hermes/google-classroom) — Manage classes, coursework, and students
- [Google Calendar](https://claw-link.dev/hermes/google-calendar) — Create and manage calendar events
- [Google Sheets tools](https://claw-link.dev/hermes/google-sheets) — Read and write spreadsheet data