Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Google Forms

Receive form responses from Google Forms

CategoryForms And Surveys
AuthenticationOAuth 2.0, custom
Version0.6.0
Published scopes3 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Google Forms with Flows360

Receive form responses from Google Forms

Use the Google Forms connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 1 trigger.

Available actions

  • Get Form
  • List Form Responses
  • Get Form Response
  • Custom API Call

Available triggers

  • New Response

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Google Forms
  • Package: @activepieces/piece-google-forms@0.6.0
  • Exact artifact digest: sha256:a315efb0e6b1028138d1b7bd9cae67255bb500be419d4c4d38f28360ef871f3a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2, CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Form (forms_get_form), Fetch a form's full structure: title, settings, items with their indices and itemIds, question IDs, and current revisionId. Classification: read.
  • List Form Responses (forms_list_responses), List submitted responses for a form, with each response's responseId, timestamps, and answers keyed by questionId. Classification: read.
  • Get Form Response (forms_get_response), Fetch one submission by its responseId, including all answers keyed by questionId and submission timestamps. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Response, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0, custom
Supported objects5
Supported actionsNot published
Triggers1

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

https://www.googleapis.com/auth/forms.responses.readonlyhttps://www.googleapis.com/auth/drive.readonlyemail

Authentication profiles

connection · oauth2

OAuth scopes: https://www.googleapis.com/auth/forms.responses.readonly, https://www.googleapis.com/auth/drive.readonly, email

connection_2 · custom
  • Service Account JSON Key Required
  • User Email Optional

Supported objects

ObjectReadWriteNotes
Get Form Yes No Fetch a form's full structure: title, settings, items with their indices and itemIds, question IDs, and current revisionId.
List Form Responses Yes No List submitted responses for a form, with each response's responseId, timestamps, and answers keyed by questionId.
Get Form Response Yes No Fetch one submission by its responseId, including all answers keyed by questionId and submission timestamps.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Response Yes No polling trigger declared by the pinned package.

Triggers

New Response · Poll

Triggers when there is new response

Inputs

  • form_id · string
  • include_team_drives · boolean

Setup

Setup

  1. Add the Google Forms connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Service Account JSON Key (serviceAccount), required.
  • User Email (userEmail), optional.

OAuth scopes

  • https://www.googleapis.com/auth/forms.responses.readonly
  • https://www.googleapis.com/auth/drive.readonly
  • email
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-google-forms@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Google Forms connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-google-forms@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com