# Google Forms integrations: forms and responses

> Create a form and create a watch in Google Forms. Connect Google Forms to the rest of your operations stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/google-forms-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Google Forms is Google Workspace's survey and form builder for collecting responses through shareable forms and quizzes. Tray.ai connects to Google Forms through the HTTP Connector, so your workflows can call the Google Forms API alongside the rest of your stack.

## Use cases

### Forms

Read, create, and update forms in Google Forms from any Tray.ai workflow. The Google Forms API covers calls such as create a form and get a form.

- Create a form
- Get a form
- Update a form

### Responses

Read responses in Google Forms from any Tray.ai workflow. The Google Forms API covers calls such as list form responses and get a form response.

- List form responses
- Get a form response

### Watches

Read, create, and delete watches in Google Forms from any Tray.ai workflow. The Google Forms API covers calls such as create a watch and list watches.

- Create a watch
- List watches
- Renew a watch

## Challenges Tray.ai solves

### Keeping Google Forms credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Google Forms credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Google Forms API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Google Forms API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Google Forms?

Yes. Tray.ai connects to Google Forms through the HTTP Connector, which calls the Google Forms API directly. Any call the Google Forms API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Google Forms?

The Google Forms API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Google Forms connector?

Google Forms runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Google Forms connector from the Google Forms API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/