Google Forms connector

1. Install the SDK

   Node.js

   npm install @scalekit-sdk/node

   Python

   pip install scalekit

   Full SDK reference: Node.js | Python

2. Set your credentials

   Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

   .env

   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>

3. Set up the connector

   Register your Google Forms credentials with Scalekit so it handles the token lifecycle. You do this once per environment.

   Dashboard setup steps

   Register your Scalekit environment with the Google Forms connector so Scalekit handles the authentication flow and token lifecycle for you. The connection name you create will be used to identify and invoke the connection programmatically. Then complete the configuration in your application as follows:

   1. Set up auth redirects

      • In Scalekit dashboard, go to AgentKit > Connections > Create Connection. Find Google Forms and click Create. Click Use your own credentials and copy the redirect URI. It looks like https://<SCALEKIT_ENVIRONMENT_URL>/sso/v1/oauth/<CONNECTION_ID>/callback.

        

      • Navigate to Google Cloud Console → APIs & Services → Credentials. Select + Create Credentials, then OAuth client ID. Choose Web application from the Application type menu.

        

      • Under Authorized redirect URIs, click + Add URI, paste the redirect URI, and click Create.

        

   2. Enable the Google Forms API

      • In Google Cloud Console, go to APIs & Services → Library. Search for “Google Forms API” and click Enable.

   3. Get client credentials

      • Google provides your Client ID and Client Secret after you create the OAuth client ID in step 1.

   4. Add credentials in Scalekit

      • In Scalekit dashboard, go to AgentKit > Connections and open the connection you created.

      • Enter your credentials:

        • Client ID (from above)
        • Client Secret (from above)
        • Permissions (scopes — see Google API Scopes reference)

        

      • Click Save.

4. Authorize and make your first call

   Node.js

   quickstart.ts

   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   
   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENV_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions
   
   const connector = 'googleforms'
   const identifier = 'user_123'
   
   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Google Forms:', link)
   process.stdout.write('Press Enter after authorizing...')
   await new Promise(r => process.stdin.once('data', r))
   
   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'googleforms_get_form',
     toolInput: { form_id: 'YOUR_FORM_ID' },
   })
   console.log(result)

   Python

   quickstart.py

   import os
   from scalekit.client import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()
   
   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENV_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions
   
   connection_name = "googleforms"
   identifier = "user_123"
   
   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Google Forms:", link_response.link)
   input("Press Enter after authorizing...")
   
   # Make your first call
   result = actions.execute_tool(
       tool_input={"form_id":"YOUR_FORM_ID"},
       tool_name="googleforms_get_form",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)

What you can do

Connect this agent connector to let your agent:

• Settings set publish — Update a Google Form’s publish settings: whether the form is published and whether it is currently accepting responses
• Watch renew — Renew an existing watch on a Google Form for another seven days from now
• List watches, responses — List the watches configured on a Google Form
• Delete watch — Delete a watch from a Google Form, immediately stopping Pub/Sub notifications for that event type
• Create watch, form — Create a watch on a Google Form that publishes a Cloud Pub/Sub notification when the form’s schema changes or a new response is submitted
• Update batch — Apply a batch of update requests to a Google Form in a single atomic call

Common workflows

Proxy API call

Node.js

const result = await actions.request({
  connectionName: 'googleforms',
  identifier: 'user_123',
  path: '/v1/forms',
  method: 'GET',
});
console.log(result);

Python

result = actions.request(
    connection_name='googleforms',
    identifier='user_123',
    path="/v1/forms",
    method="GET"
)
print(result)

Execute a tool

Node.js

const result = await actions.executeTool({
  connector: 'googleforms',
  identifier: 'user_123',
  toolName: 'googleforms_create_form',
  toolInput: {},
});
console.log(result);

Python

result = actions.execute_tool(
    connection_name='googleforms',
    identifier='user_123',
    tool_name='googleforms_create_form',
    tool_input={},
)
print(result)

Google OAuth consent screen verification

Before you use your own Google OAuth credentials in production, understand what end users see on Google’s consent screen when they authorize a connected account.

Audience type	Consent screen behavior	When to use
Internal	Shows your App Name and logo from Branding settings	Only users in your Google Workspace or Cloud Identity organization can authorize the connector
External	Shows {env_name}.scalekit.dev until Google verifies your app	Any user with a Google account can authorize the connector

Why External is required for most AgentKit connectors:

• Internal restricts authorization to users in your Google Workspace or Cloud Identity organization. Users with @gmail.com or other Google accounts outside your organization cannot complete OAuth.
• External is required when end users outside your organization authorize tool access through connected accounts.
• Organization-managed OAuth clients follow the same rules as personal or developer OAuth clients. Switching to an org-owned client does not bypass Google verification.
• Until Google completes verification of your External app, users see scalekit.dev on the consent screen. After verification, your App Name and logo appear.

Separate from Scalekit domain verification

This is Google’s OAuth consent screen behavior—not Scalekit’s. Custom domain controls your Scalekit environment URL for MCP auth branding. It does not replace Google’s app verification for OAuth consent screens.

During development:

• Add Test users under APIs & Services → OAuth consent screen while publishing status is Testing.
• On unverified apps, users can click Advanced → Go to app (unsafe) to proceed during testing.
• Google Workspace admins may need to allowlist your OAuth client.

For Google’s verification requirements and timeline, refer to Google’s OAuth consent screen verification guide.

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

googleforms_batch_update_form#Apply a batch of update requests to a Google Form in a single atomic call. This is the only way to add, edit, move, or delete questions and other items on a form. Returns a reply for each request in the same order they were submitted.4 params▾

Apply a batch of update requests to a Google Form in a single atomic call. This is the only way to add, edit, move, or delete questions and other items on a form. Returns a reply for each request in the same order they were submitted.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form to update

requestsarrayrequiredOrdered list of update requests to apply. Each item is a Forms API Request object, e.g. {"createItem": {...}} or {"updateFormInfo": {...}}

include_form_in_responsebooleanoptionalWhether the response should include the updated form, including its full item list

required_revision_idstringoptionalIf set, the update is rejected unless the form's current revision ID matches this value, protecting against concurrent edits

googleforms_create_form#Create a new Google Form with a title and optional document title. Returns the new form's ID and metadata.2 params▾

Create a new Google Form with a title and optional document title. Returns the new form's ID and metadata.

NameTypeRequiredDescription

titlestringrequiredThe title of the form shown to respondents

document_titlestringoptionalThe title of the document shown in Google Drive (defaults to the form title if not provided)

googleforms_create_watch#Create a watch on a Google Form that publishes a Cloud Pub/Sub notification when the form's schema changes or a new response is submitted. Watches expire seven days after creation unless renewed, and a form allows at most one watch per event type per project.4 params▾

Create a watch on a Google Form that publishes a Cloud Pub/Sub notification when the form's schema changes or a new response is submitted. Watches expire seven days after creation unless renewed, and a form allows at most one watch per event type per project.

NameTypeRequiredDescription

event_typestringrequiredThe type of form event that triggers a notification. One of: 'SCHEMA' (form content/settings changes) or 'RESPONSES' (a new response is submitted).

form_idstringrequiredThe ID of the Google Form to watch

topic_namestringrequiredThe fully qualified name of the Cloud Pub/Sub topic to publish notifications to

watch_idstringoptionalOptional ID to assign to the new watch (4-63 lowercase letters, digits, or hyphens). If omitted, one is auto-generated.

googleforms_delete_watch#Delete a watch from a Google Form, immediately stopping Pub/Sub notifications for that event type. This cannot be undone; a new watch would need to be created to resume notifications.2 params▾

Delete a watch from a Google Form, immediately stopping Pub/Sub notifications for that event type. This cannot be undone; a new watch would need to be created to resume notifications.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form the watch belongs to

watch_idstringrequiredThe ID of the watch to delete

googleforms_get_form#Get the structure and metadata of a Google Form including its title, description, and all questions.1 param▾

Get the structure and metadata of a Google Form including its title, description, and all questions.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form to retrieve

googleforms_get_response#Get a single response submitted to a Google Form by its response ID. Returns the respondent's answers for all questions.2 params▾

Get a single response submitted to a Google Form by its response ID. Returns the respondent's answers for all questions.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form

response_idstringrequiredThe ID of the specific response to retrieve

googleforms_list_responses#List all responses submitted to a Google Form. Returns response IDs, submission timestamps, and answer values for each respondent.4 params▾

List all responses submitted to a Google Form. Returns response IDs, submission timestamps, and answer values for each respondent.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form to list responses for

filterstringoptionalFilter responses by submission time. Format: timestamp > 2026-01-01T00:00:00Z

page_sizeintegeroptionalMaximum number of responses to return (max 5000)

page_tokenstringoptionalToken for retrieving the next page of results

googleforms_list_watches#List the watches configured on a Google Form. A form can have at most one active watch per event type (SCHEMA or RESPONSES) per project.1 param▾

List the watches configured on a Google Form. A form can have at most one active watch per event type (SCHEMA or RESPONSES) per project.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form whose watches to list

googleforms_renew_watch#Renew an existing watch on a Google Form for another seven days from now. Watches expire seven days after creation (or after the last renewal) unless renewed again.2 params▾

Renew an existing watch on a Google Form for another seven days from now. Watches expire seven days after creation (or after the last renewal) unless renewed again.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form the watch belongs to

watch_idstringrequiredThe ID of the watch to renew

googleforms_set_publish_settings#Update a Google Form's publish settings: whether the form is published and whether it is currently accepting responses. Legacy forms created before publish settings existed are not supported.4 params▾

Update a Google Form's publish settings: whether the form is published and whether it is currently accepting responses. Legacy forms created before publish settings existed are not supported.

NameTypeRequiredDescription

form_idstringrequiredThe ID of the Google Form to update

is_publishedbooleanrequiredWhether the form is published and viewable by anyone with the link

is_accepting_responsesbooleanoptionalWhether the form is currently accepting responses. Can only be true if the form is published.

update_maskstringoptionalOptional field mask limiting which publishSettings fields to update, e.g. 'publishState'. If omitted, all provided fields are updated.