> 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/form-builder/adding-a-webhook-to-a-form.md).

# Adding a Webhook to a Form

1. Go to **Settings → Webhooks** in the Form Builder.
2. Click **Add Webhook**.
3. Create a **Custom Webhook** in your workflow automation platform and copy the generated webhook URL.
4. Paste the webhook URL in the Form Builder.
5. Select when the webhook should trigger:
   * **Form Submission** – when the form is completely submitted.
   * **Partial Submission** – when the user leaves the form incomplete.
6. For partial submissions, configure the **delay time** before the webhook is triggered.
7. Click **Add Webhook** and save the form.
8. Submit the form to test the integration.
9. In the workflow platform, use **Capture Incoming Webhook** to receive and verify the submitted form data.
10. Once the webhook is received successfully, save the captured data and continue building your workflow, such as sending a **WhatsApp message**.

{% embed url="<https://www.youtube.com/watch?v=NYLrVz8dpog>" %}


---

# 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/form-builder/adding-a-webhook-to-a-form.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.