Google Forms is a web-based form and survey tool that is part of the Google Workspace suite of productivity applications. It allows users to create, share, and collect responses to forms, surveys, quizzes, and questionnaires. The Google Forms API is a RESTful interface that allows applications to programmatically create and modify forms, retrieve form structure and question definitions, and access form responses. Used by organizations of all sizes for data collection, feedback gathering, event registration, and assessments, Google Forms integrates seamlessly with Google Sheets and other Google Workspace tools. The API enables data pipelines that extract form responses for analysis, reporting, and downstream processing in business intelligence platforms and data warehouses.
Power end-to-end data operations for your Google Forms API with Nexla. Our bi-directional Google Forms connector is purpose-built for Google Forms, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Google Forms or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Google Forms workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Google Forms API credential in Nexla, you must set up OAuth 2.0 authentication in Google Cloud Console. The Google Forms API uses OAuth 2.0 to authorize access to form data, requiring you to create a Google Cloud project, enable the Forms API, configure an OAuth consent screen, and obtain client credentials.
To obtain the required OAuth 2.0 credentials for the Google Forms API:
Sign in to Google Cloud Console: Navigate to https://console.cloud.google.com/ and sign in with your Google account. If you do not yet have a Google Cloud project, click Select a project at the top of the page, then click New Project to create one.
Create or Select a Project: In the Google Cloud Console, select an existing project from the project dropdown at the top of the page, or click New Project to create a new one. Enter a descriptive project name (e.g., "Nexla Google Forms Integration") and click Create.
Enable the Google Forms API: Navigate to APIs & Services > Library in the left navigation menu. Search for "Google Forms API" and click on the result. Click Enable to activate the API for your project.
The Google Forms API must be enabled in your Google Cloud project before you can create credentials or make API calls. If the API is not enabled, all requests will return a 403 error.
Configure the OAuth Consent Screen: Navigate to APIs & Services > OAuth consent screen in the left navigation menu. This screen defines how your application appears to users during the authorization process.
Select the appropriate user type:
Internal — available only for Google Workspace organizations; limits access to users within your organization.
External — available to any Google account user; requires verification for production apps with more than 100 users.
Click Create and fill in the required application information:
App name: Enter a descriptive name (e.g., "Nexla Forms Connector").
User support email: Enter your email address.
Developer contact information: Enter your email address.
Click Save and Continue to proceed to the Scopes step.
Click Add or Remove Scopes and add the following scopes based on your intended use:
https://www.googleapis.com/auth/forms.body — Read and write access to form structure and settings.
https://www.googleapis.com/auth/forms.body.readonly — Read-only access to form structure and settings.
https://www.googleapis.com/auth/forms.responses.readonly — Read-only access to form responses.
https://www.googleapis.com/auth/drive — Full access to Google Drive (required to access forms stored in Drive).
https://www.googleapis.com/auth/drive.readonly — Read-only access to Google Drive files.
For most read-only data ingestion use cases in Nexla, adding https://www.googleapis.com/auth/forms.responses.readonly and https://www.googleapis.com/auth/forms.body.readonly is sufficient.
Click Update, then click Save and Continue to proceed.
If your app is in testing mode, add the Google accounts that should be allowed to authorize the app under Test users. Click Save and Continue.
Review the summary on the final step and click Back to Dashboard.
Create OAuth 2.0 Credentials: Navigate to APIs & Services > Credentials in the left navigation menu. Click Create Credentials, then select OAuth client ID.
Select Web application as the application type.
Enter a descriptive name for the OAuth client (e.g., "Nexla Forms OAuth Client").
Under Authorized redirect URIs, add the Nexla redirect URI. This URI is provided by Nexla and is used to receive the authorization code after the user grants consent.
Click Create to generate the credentials.
Copy both the Client ID and Client Secret displayed in the confirmation dialog.
Important
Copy the Client ID and Client Secret immediately when they are displayed. The Client Secret cannot be retrieved again after you close the dialog. Store these credentials securely and never share them publicly or commit them to version control systems.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your OAuth 2.0 Client ID in the Client ID field. This is the client identifier obtained from the Google Cloud Console Credentials page when you created the OAuth 2.0 client.
Enter your OAuth 2.0 Client Secret in the Client Secret field. This is the secret value obtained from the Google Cloud Console Credentials page when you created the OAuth 2.0 client.
The Client ID and Client Secret are sensitive credentials that authenticate Nexla with Google's OAuth 2.0 server. Keep these values secure and do not share them with unauthorized users.
Click Save to initiate the OAuth 2.0 authorization flow. Nexla will redirect you to Google's authorization page, where you will need to:
Sign in with the Google account that has access to the Google Forms you want to integrate with Nexla.
Review the permissions requested by Nexla, which correspond to the scopes configured on your OAuth consent screen.
Click Allow to grant Nexla access to your Google Forms data.
You will be redirected back to Nexla, and the credential will be saved with the OAuth access and refresh tokens.
The OAuth authorization grants Nexla permission to access your Google Forms data according to the scopes you configured. Nexla stores the authorization tokens securely and automatically refreshes them when needed, so you will not need to re-authorize frequently.
Once the OAuth authorization flow is completed, the credential is saved and will appear in a tile on the Authenticate screen during data source/destination creation, where it can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Google Forms API connector tile, then select the credential that will be used to connect to the Google Forms API, and click Next; or, create a new Google Forms API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Google Forms API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Forms
Returns a list of all Google Forms accessible to the authenticated user. Use this endpoint to discover and inventory forms across a Google Workspace account.
Response data is extracted from $.forms[*] — each element represents one form with its ID, title, and revision information.
This endpoint returns form metadata only, not response data. To retrieve submitted responses, use the List Form Responses endpoint.
List Form Responses
Returns all responses submitted to a specific Google Form. Use this endpoint to ingest survey results, quiz answers, or registration submissions for a given form.
Response data is extracted from $.responses[*] — each element represents one form submission including all answer values and respondent metadata.
Configure the following parameter: Form ID — the unique identifier of the Google Form whose responses you want to ingest. The form ID can be found in the form's browser URL between /d/ and /edit.
Use the filter query parameter with a timestamp to incrementally ingest only new responses. For example, append ?filter=timestamp>2024-01-01T00:00:00Z or use a date/time macro to fetch responses submitted since the last run.
Retrieve a single form by ID, including all items/questions.
Retrieves the complete structure of a specific Google Form, including all question items, settings, and metadata. Use this endpoint to audit form definitions or extract question schemas.
Response data is extracted from $ (the root object) — the response represents a single form with all its items and configuration.
Configure the following parameter: Form ID — the unique identifier of the Google Form to retrieve.
This endpoint returns the form definition, not the response data submitted by users. To retrieve user submissions, use the List Form Responses endpoint instead.
Retrieve a single form response by ID.
Retrieves a specific individual response submitted to a Google Form by its response ID. Use this endpoint when you need to fetch or reprocess a single known response.
Response data is extracted from $ (the root object).
Configure the following parameters: Form ID — the unique identifier of the Google Form; Response ID — the unique identifier of the specific response to retrieve.
Response IDs can be obtained by first calling the List Form Responses endpoint to retrieve all response IDs for a given form.
List all active watches on a form.
Returns all active push notification watches configured on a specific Google Form. Use this endpoint to audit or manage watch subscriptions for a form.
Response data is extracted from $.watches[*] — each element represents one active watch with its configuration and expiry details.
Configure the following parameter: Form ID — the unique identifier of the Google Form whose watches you want to list.
Watches expire after seven days if not renewed. Use the Renew an existing watch before it expires destination endpoint to extend an active watch before it lapses.
Get Reconciliation Report
Retrieves a specific reconciliation report from the Google Travel Partner API, with optional matched prices, non-scoring, and pixel data. Use this endpoint to ingest hotel booking reconciliation data.
Sends a GET request to the Travel Partner API reconciliation reports endpoint using the specified report name.
Response data is extracted from $ (the root object).
Configure the following parameters: Report Name — the resource name of the reconciliation report; Include Matched Prices, Include Non-Scoring, Include Pixels — optional flags to expand the report data returned.
This endpoint is part of the Google Travel Partner API and requires Travel Partner API access enabled in your Google Cloud project.
Query Free Booking Links Report
Queries free booking links report data from the Google Travel Partner API with optional aggregation, filtering, and pagination. Use this endpoint to analyze hotel free booking link performance metrics.
Sends a GET request to the Travel Partner API free booking links report endpoint.
Response data is extracted from $.reportRows[*] — each element represents one row of report data.
Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By — optional aggregation dimensions; Filter — optional filter expression; Page Size and Page Token — pagination controls.
This endpoint is part of the Google Travel Partner API. Ensure your credential has the required Travel Partner API scopes enabled.
Query Participation Report
Queries participation report data from the Google Travel Partner API with optional aggregation, filtering, and pagination. Use this endpoint to monitor hotel participation status and eligibility metrics.
Sends a GET request to the Travel Partner API participation report endpoint.
Response data is extracted from $.reportRows[*] — each element represents one row of report data.
Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By, Filter, Page Size, Page Token — optional pagination and filtering controls.
This endpoint is part of the Google Travel Partner API. Use the Query Property Performance Report endpoint alongside this one for a comprehensive view of hotel listing health.
Query Property Performance Report
Queries property performance report data from the Google Travel Partner API with optional aggregation, filtering, and pagination. Use this endpoint to ingest impressions, clicks, and revenue data for hotel listings.
Sends a GET request to the Travel Partner API property performance report endpoint.
Response data is extracted from $.reportRows[*] — each element represents one row of report data.
Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By, Filter, Page Size, Page Token — optional aggregation and pagination controls.
This endpoint is part of the Google Travel Partner API and requires Travel Partner API access. Combine with the Participation Report for a complete picture of property listing performance.
List Account Links
Returns all account links for a specified Google Travel Partner account. Use this endpoint to retrieve the relationships between a Travel Partner account and linked external accounts.
Sends a GET request to the Travel Partner API account links endpoint for the specified account.
Response data is extracted from $.accountLinks[*] — each element represents one account link with its configuration and status.
Configure the following parameter: Account Name — the resource name of the Travel Partner account whose links you want to retrieve.
This endpoint is part of the Google Travel Partner API. Account Name follows the format accounts/{account_id}.
List Brands
Returns all brands associated with a specified Google Travel Partner account. Use this endpoint to retrieve brand definitions, display names, and icon information for hotel portfolio management.
Sends a GET request to the Travel Partner API brands endpoint for the specified account.
Response data is extracted from $.brands[*] — each element represents one brand with its name, display names, and approval state.
Configure the following parameter: Account Name — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API. Brand information is used to categorize and display hotel properties across Google travel surfaces.
List Hotel Views
Returns a paginated list of hotel views for a specified Google Travel Partner account with optional filtering. Use this endpoint to retrieve the status and configuration of hotel property listings.
Sends a GET request to the Travel Partner API hotel views endpoint for the specified account.
Response data is extracted from $.hotelViews[*] — each element represents one hotel view with its property details and status.
Configure the following parameters: Parent — the resource name of the Travel Partner account; Filter — optional filter expression; Page Size and Page Token — pagination controls.
This endpoint is part of the Google Travel Partner API. Use the optional Filter parameter to narrow results by hotel status, partner hotel ID, or other supported attributes.
Summarize Hotel Views
Returns a summary of hotel views metrics and statistics for a specified Google Travel Partner account. Use this endpoint to get aggregate counts and status breakdowns across all hotel properties.
Sends a GET request to the Travel Partner API hotel views summary endpoint and returns a single summary object.
Response data is extracted from $ (the root object).
Configure the following parameter: Parent — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API and returns aggregate statistics rather than individual hotel records. Use List Hotel Views to retrieve per-property details.
List Icons
Returns all icons available under a specified Google Travel Partner account. Use this endpoint to retrieve icon assets used in brand and hotel property configurations.
Sends a GET request to the Travel Partner API icons endpoint for the specified account.
Response data is extracted from $.icons[*] — each element represents one icon with its URI and approval state.
Configure the following parameter: Parent — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API. Icons must be approved by Google before they can be associated with a brand or displayed on travel surfaces.
List Price Accuracy Views
Returns a list of price accuracy views for a specified Google Travel Partner account. Use this endpoint to monitor how accurately hotel prices are being reported across Google travel surfaces.
Sends a GET request to the Travel Partner API price accuracy views endpoint for the specified account.
Response data is extracted from $.priceAccuracyViews[*] — each element represents one price accuracy record with accuracy scores and associated date ranges.
Configure the following parameter: Parent — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API. Price accuracy scores affect hotel listing eligibility and ranking on Google travel surfaces.
Summarize Price Accuracy Views
Returns a summary of price accuracy metrics and statistics for a specified Google Travel Partner account. Use this endpoint to get a high-level overview of pricing accuracy performance across all properties.
Sends a GET request to the Travel Partner API price accuracy views summary endpoint and returns a single summary object.
Response data is extracted from $ (the root object).
Configure the following parameters: Parent — the resource name of the Travel Partner account; Data Format Version — optional version parameter for the response format.
This endpoint is part of the Google Travel Partner API and returns aggregate statistics rather than per-property records. Use List Price Accuracy Views for per-property detail.
List Price Coverage Views
Returns a list of price coverage views for a specified Google Travel Partner account. Use this endpoint to analyze the proportion of user queries for which hotel prices are being returned.
Sends a GET request to the Travel Partner API price coverage views endpoint for the specified account.
Response data is extracted from $.priceCoverageViews[*] — each element represents one price coverage snapshot with coverage percentage and associated date.
Configure the following parameter: Parent — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API. Low price coverage can indicate issues with price feed delivery or query matching.
Get Latest Price Coverage View
Returns the most recent price coverage view data for a specified Google Travel Partner account. Use this endpoint to quickly retrieve the current price coverage status without pagination.
Sends a GET request to the Travel Partner API latest price coverage view endpoint and returns a single coverage object.
Response data is extracted from $ (the root object).
Configure the following parameter: Parent — the resource name of the Travel Partner account.
This endpoint is part of the Google Travel Partner API and returns only the latest snapshot. Use List Price Coverage Views to retrieve historical coverage data.
List Reconciliation Reports
Returns a paginated list of reconciliation reports for a specified Google Travel Partner account. Use this endpoint to retrieve a history of hotel booking reconciliation reports within a date range.
Sends a GET request to the Travel Partner API reconciliation reports endpoint for the specified account.
Response data is extracted from $.reconciliationReports[*] — each element represents one report with its name and creation metadata.
Configure the following parameters: Parent — the resource name of the Travel Partner account; Start Date and End Date — optional date range filters to limit the reports returned.
This endpoint is part of the Google Travel Partner API. Use Start Date and End Date to retrieve reports for a specific period, which is useful for scheduled reconciliation workflows.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Google Forms API data sources can also be manually configured to ingest data from any valid Google Forms API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Common Google Forms API endpoints include https://forms.googleapis.com/v1/forms/{formId} (form structure, items, and settings), https://forms.googleapis.com/v1/forms/{formId}/responses (all responses to a form), and https://forms.googleapis.com/v1/forms/{formId}/responses/{responseId} (a single response). The form ID is embedded in the form's browser URL between /d/ and /edit — for example, in https://docs.google.com/forms/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms/edit, the form ID is 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms.
The forms.responses.list endpoint supports a filter query parameter that accepts RFC 3339 timestamps (e.g., filter=timestamp>2024-01-01T00:00:00Z) — date/time macros are useful here to incrementally retrieve only responses submitted since the last run. Set the path to data to $.responses[*] to extract individual response records from that endpoint, or $.items[*].questionItem to extract individual question items from a form's structure. If a top-level field such as nextPageToken falls outside the configured path to data, it can be preserved as metadata on each record.
The Google Forms API Authorization header is added automatically based on your OAuth credential and does not need to be included in the request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Google Forms API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Google Forms API destination, and select the Send to Destination option from the menu. Select the Google Forms API connector from the list of available destination connectors, then select the credential that will be used to connect to the Google Forms API, and click Next; or, create a new Google Forms API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Google Forms API endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create a new Google Form.
Creates a new Google Form using the data provided by Nexla. Use this endpoint to programmatically generate forms as part of automated workflows.
The request body must include an info object with at least a title field.
The credential used must include the https://www.googleapis.com/auth/forms.body OAuth scope to create forms. The newly created form's ID is returned in the API response.
Update form items/settings via a batch of requests
Adds, updates, or deletes items and settings in an existing Google Form via a batch of update requests. Use this endpoint to programmatically modify form structure or configuration.
Configure the following parameter: Form ID — the unique identifier of the Google Form to update.
Each update request in the batch must specify the operation type (e.g., createItem, updateItem, deleteItem). The credential must include the https://www.googleapis.com/auth/forms.body scope.
Create a watch for form/response change notifications
Creates a push notification watch on a specific Google Form so that your application is notified when the form or its responses change. Use this endpoint to set up event-driven data pipelines triggered by new form submissions.
Configure the following parameter: Form ID — the unique identifier of the Google Form on which to create the watch.
Watches expire after seven days. Use the Renew an existing watch before it expires endpoint to extend the watch before expiration. The watch target (e.g., Cloud Pub/Sub topic) must be configured in the request body.
Renew an existing watch before it expires
Renews an existing push notification watch on a Google Form for another seven days before it expires. Use this endpoint in scheduled workflows to maintain continuous form change notifications.
Configure the following parameters: Form ID — the unique identifier of the Google Form; Watch ID — the unique identifier of the watch to renew.
Schedule this destination to run before the watch expiry (every 5–6 days) to ensure uninterrupted push notifications. Watch IDs can be retrieved using the List all active watches on a form source endpoint.
Delete a watch on a form.
Permanently deletes a push notification watch on a specific Google Form. Use this endpoint to clean up watches that are no longer needed.
Configure the following parameters: Form ID — the unique identifier of the Google Form; Watch ID — the unique identifier of the watch to delete.
This action is permanent and cannot be undone. Deleting a watch stops all push notifications associated with it. Retrieve active watch IDs using the List all active watches on a form source endpoint before deletion.
Set Hotels Live on Google
Activates hotel properties to appear live on Google travel surfaces for a Travel Partner account. Use this endpoint to control the live status of hotel listings programmatically.
Sends a request to the Google Travel Partner API to update the live status of specified hotel properties.
Configure the following parameters: Account ID — the Travel Partner account identifier; Live on Google — flag to set the live status; Partner Hotel IDs — the list of hotel IDs to activate or deactivate.
This endpoint is part of the Google Travel Partner API and requires Travel Partner API access enabled in your Google Cloud project.
Update Brand
Updates an existing Travel Partner brand with new display names, icons, and approval state information. Use this endpoint to manage hotel brand configurations programmatically.
Sends a PATCH or PUT request to the Travel Partner API brands endpoint with the updated brand data.
Configure the following parameters: Brand Name — the resource name of the brand to update; Update Mask — the list of fields to update; additional optional fields for display names, icons, and states.
This endpoint is part of the Google Travel Partner API. Use the Allow Missing parameter set to true to create the brand if it does not already exist (upsert behavior).
Create Account Link
Creates a new account link between a Google Travel Partner account and an external account. Use this endpoint to establish programmatic linkages between Travel Partner accounts and partner systems.
Sends a POST request to the Travel Partner API account links endpoint with the link configuration in the request body.
Configure the following parameter: Account Name — the resource name of the Travel Partner account under which the link will be created.
This endpoint is part of the Google Travel Partner API. The request body must include the external account reference and the desired link type.
Create Brand
Creates a new brand under a specified Google Travel Partner account with display names, icons, and metadata. Use this endpoint to programmatically add hotel brands to a Travel Partner account.
Sends a POST request to the Travel Partner API brands endpoint with the new brand definition in the request body.
Configure the following parameters: Parent — the resource name of the Travel Partner account; additional optional fields for display names, icons, and brand metadata.
This endpoint is part of the Google Travel Partner API. Newly created brands must go through Google's approval process before display names and icons are activated on travel surfaces.
Verify Listing
Verifies a hotel listing for a specified Travel Partner account by submitting XML listing data. Use this endpoint to validate hotel property data against Google's listing requirements.
Sends a POST request to the Travel Partner API verify listing endpoint with the XML listing content in the request body.
Configure the following parameters: Parent — the resource name of the Travel Partner account; XML Listing — the hotel listing data in XML format.
This endpoint is part of the Google Travel Partner API. The XML listing must conform to Google's hotel feed schema. Verification results indicate whether the listing data meets Google's quality and format requirements.
Create Reconciliation Report
Creates a new reconciliation report for a specified Google Travel Partner account with provided file contents. Use this endpoint to submit hotel booking reconciliation data to Google.
Sends a POST request to the Travel Partner API reconciliation reports endpoint with the report data in the request body.
Configure the following parameters: Parent — the resource name of the Travel Partner account; File Contents — the report file data; File Name — the name of the report file; Name — the resource name for the new report.
This endpoint is part of the Google Travel Partner API. Reconciliation reports are used to match Google's booking data with your own records for billing and performance verification.
Google Forms API destinations can also be manually configured to send data to any valid Google Forms API endpoint not included in the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The base URL for the Google Forms API is https://forms.googleapis.com/v1/. Common write endpoints are Create a Form (POST /forms), Batch Update a Form (POST /forms/{formId}:batchUpdate, used to add, update, or delete questions and form settings), and Create a Watch (POST /forms/{formId}/watches, used to receive push notifications on form or response changes). The Google Forms API accepts JSON for all write operations, and write requests require a credential with the appropriate write scope (e.g., https://www.googleapis.com/auth/forms.body). The Authorization header is added automatically based on your OAuth credential and does not need to be included in the request headers.
Record batching is particularly useful for the Batch Update a Form endpoint, which accepts multiple update operations in a single call: select the Property Inside JSON Object grouping algorithm with the property name requests, since the batchUpdate API expects an array of request objects under that key.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Google Forms API endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Google Forms API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
