> 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/chat-widget/how-to-send-pre-chat-form-data-to-a-webhook-url-or-to-automations-builder.md).

# How To Send Pre Chat Form Data To A Webhook Url Or To Automations Builder ?

To trigger an automation workflow or send data to a webhook when a widget pre-chat form is submitted:

1. On the widgets page, click on the **webhook icon**.
2. Obtain a webhook from the **automations builder**.
3. Enter the webhook URL and specify when the data should be sent (e.g., after session completion).
4. Click "**Add webhook**" and select the **pre-chat form** as the session.
5. Click "Capture incoming hook" in the automations builder to receive data upon form submission or session completion.

Data received includes IP, page URL, pre-chat questions, and answers. You can use this data for various actions, such as populating a Google sheet or sending a WhatsApp message.

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


---

# 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/chat-widget/how-to-send-pre-chat-form-data-to-a-webhook-url-or-to-automations-builder.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.