> 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/faq.md).

# FAQ

<details>

<summary>How do I find my Google Form ID?</summary>

Open your form in Google Forms. Look at the URL in your browser — it will look something like `https://docs.google.com/forms/d/1A2B3C4D5E6F/edit`. The Form ID is the long string between `/d/` and the next `/`. Copy just that part and paste it into the Form IDs field in Coupler.io.

</details>

<details>

<summary>Can I pull responses from multiple forms at once?</summary>

Yes. In the Form IDs field, enter each Form ID on a separate line. Coupler.io will pull data from all of them. If you want the responses combined into a single table, use the **Append** transformation. If you want them in separate tables, set up separate sources or data flows.

</details>

<details>

<summary>Will I get all historical responses or only new ones?</summary>

Coupler.io pulls all available responses from the form each time the data flow runs — not just new ones since the last sync. This means your destination always reflects the complete response dataset, not an incremental update.

</details>

<details>

<summary>Can I export responses from a form I don't own?</summary>

Yes, as long as the form has been shared with the Google account you connected to Coupler.io. You need at least Viewer access on the form. If you don't see responses, ask the form owner to verify your sharing permissions.

</details>

<details>

<summary>What happens if I add new questions to a form after setting up the data flow?</summary>

New questions will appear as additional columns or rows in your next sync. The structure of the Forms entity updates automatically. For Form responses, older submissions won't have answers for the new questions — those fields will be empty for pre-existing responses.

</details>

<details>

<summary>Can I analyze open-ended responses automatically?</summary>

Yes. Route your Form responses entity to an AI destination — ChatGPT, Claude, Gemini, Perplexity, or others supported by Coupler.io. These can summarize themes, classify sentiment, or extract key points from free-text answers at scale.

</details>

<details>

<summary>Does Coupler.io support Google Forms quiz scoring?</summary>

Yes. If your form is set up as a quiz, the Form responses entity includes a `score` field with the points awarded per response. You can use this to track scores in Google Sheets or aggregate results in BigQuery.

</details>

{% hint style="info" %}
For a full list of available fields and what each one contains, see the [Data Overview](/sources/category/surveys/google-forms/data-overview.md) article. For connection errors or missing data, check [Common Issues](/sources/category/surveys/google-forms/common-issues.md).
{% endhint %}


---

# 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/faq.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.
