Integration reference

Google Forms Trigger and Action reference

Start Workflows from new or edited form responses, monitor form changes, and create, update, publish, or read Google Forms.

3 Triggers8 ActionsManifests: Trigger v1 · Action v1

Authentication

Connect the Google account that owns or can edit the selected forms, then approve Forms and Drive metadata access.

  • Trigger account type: oauth2; reconnect by oauth.
  • Action connection type: oauth2; available modes: Connected Google Forms account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: openid, email, profile, https://www.googleapis.com/auth/forms.body.readonly, https://www.googleapis.com/auth/forms.responses.readonly, https://www.googleapis.com/auth/drive.metadata.readonly.

View 3 OAuth scopes used by current Actions

https://www.googleapis.com/auth/drive.metadata.readonly, https://www.googleapis.com/auth/forms.body, https://www.googleapis.com/auth/forms.responses.readonly

View 3 provider permissions or credential requirements

https://www.googleapis.com/auth/drive.metadata.readonly, https://www.googleapis.com/auth/forms.body, https://www.googleapis.com/auth/forms.responses.readonly

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Google Forms as a Trigger

The current provider manifest contains 3 available Trigger definitions. Representative definitions include:

  • New Form Response
  • New or Updated Form Response
  • Form Updated
View all 3 available Trigger definitions
TriggerManifest keyDeliveryAdditional scopes
New Form Responsegoogle_forms.new_response.pollingpollingNone declared
New or Updated Form Responsegoogle_forms.new_or_updated_response.pollingpollingNone declared
Form Updatedgoogle_forms.form_updated.pollingpollingNone declared

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Google Forms Actions

The current Action manifest contains 8 operations. Representative Actions include:

  • Create Form
  • Update Form
  • Set Publish Settings
  • List Responses
  • Get Response
  • Custom API Request
View all 8 available Action definitions
ActionManifest keyAccess and authManifest rate limit
List Formsgoogle_forms.list_formshttps://www.googleapis.com/auth/drive.metadata.readonly
FastHook-managed account
1/second
Get Formgoogle_forms.get_formhttps://www.googleapis.com/auth/forms.body
FastHook-managed account
1/second
Create Formgoogle_forms.create_formhttps://www.googleapis.com/auth/forms.body
FastHook-managed account
1/second
Update Formgoogle_forms.batch_update_formhttps://www.googleapis.com/auth/forms.body
FastHook-managed account
1/second
Set Publish Settingsgoogle_forms.set_publish_settingshttps://www.googleapis.com/auth/forms.body
FastHook-managed account
1/second
List Responsesgoogle_forms.list_responseshttps://www.googleapis.com/auth/forms.responses.readonly
FastHook-managed account
1/second
Get Responsegoogle_forms.get_responsehttps://www.googleapis.com/auth/forms.responses.readonly
FastHook-managed account
1/second
Custom API Requestgoogle_forms.custom_api_requesthttps://www.googleapis.com/auth/forms.body, https://www.googleapis.com/auth/forms.responses.readonly
FastHook-managed account
1/second

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

  1. Create a Source using a Google Forms Trigger definition.
  2. Create a Workflow with that Source as its Trigger.
  3. Add the required Google Forms Action and select the connected account.
  4. Map Trigger or earlier-Step data into the Action fields with the field picker.
  5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
  6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Google Forms.

Troubleshooting Google Forms

The account is missing or cannot be selected
Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
A resource picker is empty
Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
The editor asks for additional scopes
Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
An active Workflow returns 401, 403, or a permission error
Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
The provider returns 429 or a temporary 5xx
Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

  • Sources poll every five minutes and establish a baseline before emitting later response or form changes.
  • Response payloads keep Google question IDs as answer-map keys. Use Get Form to match those IDs to question titles.
  • Update Form accepts the official batchUpdate request array, so one Action can add, move, edit, or delete several form items atomically.
  • Google Forms stores each form as a Drive file. List Forms and the form picker require Drive metadata access.
  • Custom API Request is restricted to the official https://forms.googleapis.com/v1/forms/ path.

Next