Google Forms is a survey administration software that allows users to create and share online forms and surveys.
Google Forms is a survey administration software that allows users to create and share online forms and surveys. On Nagent, Googleforms is exposed as a fully-configurable productivity integration that any agent can call — 10 actions, and OAuth authentication. No code is required to wire Googleforms into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Googleforms to automate the kinds of tasks productivity teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Googleforms into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Googleforms, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GOOGLEFORMS_BATCH_UPDATE_FORMApplies a batch of update operations to a Google Form in a single atomic transaction. Use when you need to modify form content after creation, including: - Adding, updating, or deleting questions and other items - Modifying form metadata (title, description) - Updating form settings (quiz mode, email collection) - Reorganizing item order within the form All updates in the batch are applied together atomically. If any update fails, the entire batch is rolled back. Use writeControl for optimistic concurrency to ensure updates are applied to the expected form version. Note: The form must have the appropriate sharing settings for the authenticated user to modify it.
Input parameters
Required. The ID of the form to update.
Required. The update requests to apply to the form. Each request is a dictionary containing exactly one request type: **Available request types:** - `createItem` - Add a new item (question) to the form. Requires `item` (the item definition) and `location` (where to place it). - `updateFormInfo` - Update form metadata. Requires `info` (title, description) and `updateMask` (fields to update). - `updateSettings` - Update form settings. Requires `settings` and `updateMask`. - `updateItem` - Update an existing item. Requires `item`, `location`, and `updateMask`. - `moveItem` - Move an item to a new location. Requires `originalLocation` and `newLocation`. - `deleteItem` - Delete an item. Requires `location` with the index of the item to delete. All updates are applied atomically - if any update fails, the entire batch is rolled back.
Provides control over how write requests are executed.
Whether to return the updated form in the response. Set to true to get the complete form with all applied mutations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_CREATE_FORMCreates a new Google Form with the specified title. This action initializes an empty form that can be later populated with items (questions, sections, images, videos) using the batchUpdate endpoint. When a form is created, it is assigned a unique formId that is required for all subsequent operations on that form. As of June 30, 2026, forms created via API will default to an unpublished state, giving creators control over responder access before making the form publicly available. Use this action when you need to create a new form for collecting information, surveys, quizzes, or feedback. After creation, use the batchUpdate action to add questions and other items to the form.
Input parameters
Required. Form info object containing the title and optional document title.
Optional. Whether the form is unpublished. If set to true, the form doesn't accept responses. If set to false or unset, the form is published and accepts responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_CREATE_WATCHCreates a watch on a Google Form to receive push notifications via Cloud Pub/Sub when specified events occur. Watches notify via Cloud Pub/Sub when the form or its responses are changed. Each watch has a one-week duration after which it automatically expires and must be renewed. The calling project can have a maximum of 2 watches per form (one for SCHEMA and one for RESPONSES). Use this action when you need to set up real-time notifications for form changes or new submissions. The Pub/Sub topic must be in the same project where the form is located, and the topic must have permissions configured to allow the Forms API to publish messages.
Input parameters
Required. ID of the Form to watch. The form ID can be found in the form URL: https://docs.google.com/forms/d/{formId}/edit
Required. The Pub/Sub topic configuration for delivering notifications.
Optional. A unique ID to assign to this watch. If not specified, an ID is auto-generated. Must be 4-63 characters; valid characters are \[a-z\]\[0-9\]-.
Required. Type of event to watch for: SCHEMA monitors form structure or settings changes; RESPONSES monitors new form submissions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_DELETE_WATCHDeletes a watch from a Google Form, stopping push notifications for that watch. Use when you no longer want to receive notifications for a specific watch on a form. This action is irreversible — once deleted, the watch cannot be recovered and notifications will stop immediately. If you need to resume notifications, you must create a new watch using the CreateWatch action.
Input parameters
Required. ID of the Form that contains the watch. The form ID can be found in the form URL: https://docs.google.com/forms/d/{formId}/edit
Required. The ID of the Watch to delete. Use the ListWatches action to find existing watch IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_GET_FORMRetrieves the complete structure and metadata of a Google Form. Returns the full form definition including its title, description, all items (questions, sections, page breaks, images, videos, and display text), form settings (quiz mode, email collection), publishing state, and output-only fields such as the responder submission URL and revision ID. This action is read-only and does not modify the form. Use this action when you need to read the current configuration of a form, display its structure to users, inspect its settings, or check its publishing state before making updates.
Input parameters
Required. The unique ID of the form to retrieve. The form ID can be found in the URL after 'forms/d/' when viewing the form in Google Forms.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_GET_RESPONSERetrieves a single form response by its unique response ID. Returns complete response data including all answers provided by the respondent, their email (if collected), timestamps, and quiz scores (if applicable). Use this action when you need to fetch detailed information about a specific submission, such as viewing individual submissions, verifying response data, or building response detail views.
Input parameters
Required. The form ID of the form to retrieve a response from.
Required. The response ID to retrieve. This is the unique identifier for a specific form submission.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_LIST_RESPONSESLists all responses submitted to a Google Form with optional filtering and pagination. Use this action to retrieve multiple form submissions at once, export response data, or monitor new submissions. Supports filtering by timestamp to fetch only responses submitted after a specific time, which is useful for incremental data synchronization.
Input parameters
A filter expression to return only responses that match the specified condition. Supports timestamp > N or timestamp >= N in RFC3339 UTC 'Zulu' format (e.g., '2024-01-15T00:00:00Z'). Use this for incremental data synchronization to fetch only new responses.
Required. The ID of the Form whose responses to list. You can find the form ID in the form URL: https://forms.google.com/forms/d/{formId}/edit
The maximum number of responses to return. If unspecified, at most 5000 responses are returned. Use pageToken to iterate through pages.
A page token returned by a previous list response. Use this to retrieve the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_LIST_WATCHESLists all watches owned by the calling project for a specific Google Form. Use this action to discover existing watches, check their status and expiration times, or audit which notifications are configured for a form. Each project can have a maximum of 2 watches per form (one for each event type: SCHEMA and RESPONSES). The SCHEMA event type monitors changes to form content or settings, while RESPONSES monitors new form submissions.
Input parameters
Required. ID of the Form whose watches to list. The form ID can be found in the form URL: https://docs.google.com/forms/d/{formId}/edit
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_RENEW_WATCHRenews a watch on a Google Form, extending its expiration by one week from the time of renewal. Google Forms watches automatically expire after one week. Use this action to extend a watch before it expires, maintaining continuous push notifications. If a watch has already expired, you must create a new one instead. The renewed watch keeps the same ID, event type, and Pub/Sub topic configuration. Only the expiration time is updated.
Input parameters
Required. ID of the Form that contains the watch. The form ID can be found in the form URL: https://docs.google.com/forms/d/{formId}/edit
Required. The ID of the Watch to renew. Use the ListWatches action to find existing watch IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLEFORMS_SET_PUBLISH_SETTINGSUpdates the publishing settings of a Google Form, controlling whether the form is published (visible to others) and whether it accepts responses. Use this action to publish a draft form, unpublish a form to prevent access, or toggle response collection on/off without changing the form's visibility. Note that legacy forms created before the publish settings feature was introduced cannot use this endpoint and will return an error.
Input parameters
Required. The ID of the form to update. You can get the form ID from the Form.form_id field.
Optional. The publishSettings fields to update. Accepts: 'publishState' or '*' for all fields. If not provided, all fields are updated.
Required. The desired publish settings to apply to the form.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 50 agents privately built on Nagent that already use Googleforms.
Build on Nagent
Connect Googleforms to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Googleforms, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Googleforms is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Googleforms is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Googleforms steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Googleforms event fires, the agent kicks off automatically.
Every Googleforms action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Googleforms ships with 10 pre-built productivity actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Googleforms together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Googleforms-based workflows tailored to your business.