> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/lead-source/google-forms-integration.md).

# Google Forms Integration

#### Step 1: Create Connection

1. Go to **Lead Source**
2. Select **Google Forms Integration**
3. Click **Create Connection**
4. Enter connection name
5. Click **Create Connection**

#### Step 2: Copy Script

1. Copy the **Apps Script code** generated
2. Keep the **Webhook URL** secure

#### Step 3: Add Script in Google Form

1. Open your **Google Form (Edit Mode)**
2. Click **3 dots → Script Editor**
3. Remove existing code
4. Paste the copied script
5. Click **Save**

#### Step 4: Configure Trigger

1. Go to **Triggers**
2. Click **Add Trigger**
3. Set:
   * Function: **onSubmit**
   * Event Type: **On form submit**
4. Save and authorize

#### Step 5: Field Mapping

1. Go to **Installed Page**
2. Open **Field Mapping**
3. Map form fields (Name, Email, Phone, etc.) to CRM fields

#### Step 6: Test Setup

1. Submit a **test response** in Google Form
2. Verify fields are fetched correctly

#### Step 7: Optional Settings

* Enable **Auto Create Contact**
* Configure **Webhook (if required)**

#### Step 8: Monitor Logs

1. Go to **Logs Section**
2. Check lead data, status, and errors

* Integration is ready and live

{% embed url="<https://youtu.be/n60K_Z_PRp4>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/lead-source/google-forms-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.