How many watches can be set on a single Google Form?

Two per form per calling project: one for SCHEMA, which fires on content or settings changes, and one for RESPONSES, which fires on new submissions. Each expires after a week, so Lyro extends it with Renew Form Watch. An expired watch cannot be renewed and has to be created again.

Will a form Lyro creates be live straight away?

No. Since 30 June 2026, forms created through the API default to an unpublished state so the creator controls responder access first. Lyro publishes it and switches on response collection with Set Form Publish Settings, which legacy forms created before that setting existed cannot use and will error on.

What happens if one edit in a bulk form update fails?

The whole batch rolls back. Batch Update Form applies added, edited, deleted and reordered items plus metadata and settings changes as one atomic transaction, and Lyro can pass writeControl so the update lands only on the form revision it was written against.

What access does Lyro need on the form and the project?

Whatever the connected Google account already holds. Batch Update Form requires the form's sharing settings to permit the authenticated user to modify it, and Create Form Watch additionally needs a Cloud Pub/Sub topic in the same project as the form, with permissions allowing the Forms API to publish to it.

Googleforms MCP integration

Creates and edits forms in atomic batches, publishes them, reads submissions incrementally, and keeps Pub/Sub watches renewed.

Connect Googleforms See all integrations

10actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create a google form
Lyro creates a new Google Form for collecting customer feedback. Teams gather structured responses without manual setup.
List google form responses
Lyro retrieves all responses submitted to a Google Form. Agents review customer feedback and identify patterns.
Batch update form
Lyro applies multiple changes to a Google Form in one operation. Support teams update form fields without repeating edits.

See all 10 actions

How businesses use Googleforms + Lyro

Each card is one request a support team gets, and the Googleforms actions Lyro runs to close it.

Build a form and get it live
Lyro creates the form, then adds questions, sections, images and settings such as quiz mode or email collection in one atomic batch, and reads the finished definition back before anyone is invited.
Create a Google FormBatch Update FormGet Google Form
Read what people have submitted
Lyro lists responses filtered by timestamp so only new submissions come through on each pass, and opens a single response in full with its answers, timestamps, quiz score and collected email.
List Google Form ResponsesGet Form Response
Get told the moment a form changes
Lyro creates a Cloud Pub/Sub watch on new responses or on schema changes, audits which watches already exist with their expiry times, and renews one before its one-week window runs out.
Create Form WatchList Form WatchesRenew Form Watch
Close a form and stop the notifications
Lyro turns off response collection or unpublishes the form entirely, and deletes the watch so push notifications stop immediately rather than running until the weekly expiry.
Set Form Publish SettingsDelete Form Watch

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Googleforms actions it has and picks the ones a request needs.

01
Connect Googleforms
Authorize the Googleforms account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Googleforms actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Googleforms · Lyro

Everything else about Googleforms

Setup, permissions, and the limits of what Lyro can do inside Googleforms.

Two per form per calling project: one for SCHEMA, which fires on content or settings changes, and one for RESPONSES, which fires on new submissions. Each expires after a week, so Lyro extends it with Renew Form Watch. An expired watch cannot be renewed and has to be created again.

Every action available in Googleforms

All 10 actions your agent can call on Googleforms, straight from the live MCP connection.

Batch update form
Applies a batch of update operations to a Google Form in a single atomic transaction.
Create a google form
Creates a new Google Form with the specified title.
Create form watch
Creates a watch on a Google Form to receive push notifications via Cloud Pub/Sub when specified events occur.
Delete form watch
Deletes a watch from a Google Form, stopping push notifications for that watch.
Get google form
Retrieves the complete structure and metadata of a Google Form.
Get form response
Retrieves a single form response by its unique response ID.
List google form responses
Lists all responses submitted to a Google Form with optional filtering and pagination.
List form watches
Lists all watches owned by the calling project for a specific Google Form.
Renew form watch
Renews a watch on a Google Form, extending its expiration by one week from the time of renewal.
Set form publish settings
Updates the publishing settings of a Google Form, controlling whether the form is published (visible to others) and whether it accepts responses.