Google Forms
Create and update Google Forms, manage publish state, and read form responses.
About
Google Forms ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.google-forms- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Productivity
Overview
Google Forms creates and updates forms, manages whether a form is published and accepting responses, and reads back the responses submitted to it, against Google’s own Forms API. A form is created with just a title, then built up through explicit follow-up updates — adding, moving and deleting items, and updating form settings — since Google’s own create call accepts nothing beyond a title to begin with.
Items — questions, page breaks, images, videos and grading — are passed through as the API’s own structured JSON rather than flattened into a simplified field set, so the full range of question and grading options stays available without a second schema to maintain. Because items are addressed by position rather than by a stable id, moving or deleting one is treated as non-repeatable: running it twice acts on whatever now sits at that position, not the original item.
A user’s own Google sign-in covers personal forms, while a service account handles unattended, server-to-server runs — with the caveat that a form a service account creates has no owner who can open it in Drive unless ownership is handed to a real user afterward. Listing existing forms and reading responses round out the read side; watch subscriptions and quiz grading are left out, since the former needs infrastructure this app can’t provide and the latter is already reachable through the same item JSON.
Build with Google Forms
Three routes to the same 12 actions. The Workflow tab is generated from Google Forms's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Batch Update Form
form-batch-update Apply a raw array of Google Forms update requests in one atomic batch.
Set Publish Settings
form-set-publish-settings Publish or unpublish a form and start or stop accepting responses.
Update Form Settings
form-update-settings Turn a form into a quiz (or back) and set how respondent emails are collected.
List Forms
list-forms List Google Forms in the connected account's Drive, optionally filtered by name.
List Responses
response-list List a form's responses, optionally only those submitted after a timestamp.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Google Forms's real ids.
{
"manifestVersion": "2",
"name": "google-forms-example",
"steps": [
{
"id": "form-add-item",
"uses": {
"app": "io.w6w.google-forms",
"action": "form-add-item",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"formId": "<formId>",
"item": "<item>",
"index": "<index>"
}
}
]
}Here are some of the things you can do
-
Add Item
performform-add-item -
Batch Update Form
performform-batch-update -
Create Form
performform-create -
Get Form
readform-get -
Move Item
performform-move-item
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Google Forms, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Google Forms. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "form-create",
payload: {
title: "<value>",
// documentTitle: "<value>",
// unpublished: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action form-create --payload '{"title":"<value>"}'Give an AI agent Google Forms — without giving it Google Forms's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.google-forms#form-add-item",
"input": {
"formId": "<formId>",
"item": "<item>",
"index": "<index>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Google Forms connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Google Forms's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Google Forms itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Google Forms declares its own checks, so its health is a property of the app rather than something the host guesses at.
Google Forms platform status
Open incidents for Google Forms on the Google Workspace Status Dashboard. Unauthenticated and unsigned.