> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/surveys/google-forms.md).

# Google Forms

Google Forms is a free survey and form builder from Google that lets you collect responses, run quizzes, and gather feedback. With Coupler.io, you can pull your form structure and all response data into spreadsheets, databases, or BI tools — automatically and on a schedule.

## Why connect Google Forms to Coupler.io?

* **Centralize response data** — export submissions from one or many forms into a single destination without manual downloads
* **Automate reporting** — keep your dashboards and sheets refreshed with the latest responses without any copy-paste work
* **Combine data from multiple forms** — use Append to merge responses from different forms into one unified dataset
* **Analyze with AI** — send your response data straight to ChatGPT, Claude, Gemini, or other AI destinations for instant summarization and analysis

## Prerequisites

* A Google account with access to the forms you want to export
* The Form IDs for each form you want to connect (see the tip below on where to find these)
* Editor or Owner access on the forms — Viewer access is sufficient for reading responses

{% hint style="success" %}
Your Form ID is in the form's URL. For a URL like `https://docs.google.com/forms/d/1A2B3C4D5E/edit`, the ID is `1A2B3C4D5E` — the string between `/d/` and `/edit`.
{% endhint %}

## Quick start

{% hint style="success" %}
Start with the **Form responses** entity if your goal is to analyze submissions. Add the **Forms** entity to the same data flow if you also want question text and form structure for reference.
{% endhint %}

{% stepper %}
{% step %}
**Connect your Google account.** In Coupler.io, create a new data flow and select Google Forms as the source. Click **Connect** and sign in with the Google account that has access to your forms. Grant the requested permissions.
{% endstep %}

{% step %}
**Enter your Form IDs.** In the **Form IDs** field, paste the ID of each form you want to export — one ID per line. You can add multiple forms in a single source.
{% endstep %}

{% step %}
**Choose an entity.** Select either **Forms** (for form metadata and question structure) or **Form responses** (for individual submissions). To export both, add a second source to the same data flow.
{% endstep %}

{% step %}
**Choose a destination.** Pick where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm everything is working correctly.
{% endstep %}
{% endstepper %}

## Entities overview

| Entity             | Description                                                                       |
| ------------------ | --------------------------------------------------------------------------------- |
| **Forms**          | Form metadata including title, description, questions, and configuration settings |
| **Form responses** | Individual response submissions with answers and response metadata                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/surveys/google-forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.