> For the complete documentation index, see [llms.txt](https://docs.ipaper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipaper.io/flipbook-integration/form-integration.md).
# Form Integration
## Configuration
When using the Form module, you have to ability enable POST integration. With this setting enabled, when the users clicks the “Submit” button in the Form, the values entered by the user will be sent via a POST request to the endpoint specified under the Form Settings.
The setting needed for enabling POST integration, is shown below:
## Receiving data from Form POST integration
The values received by the endpoint, will come in form of standard Web Form values. Each value will have a key corresponding the the “Name” value of the form element. Looking at the overview of your Form, you will a list of all Name of all form fields.
{% hint style="warning" %}
**Important:**
Please note that the “Name” value is an internal name not visible by the end-user, as not to confuse with the “Label” value
{% endhint %}
For the form in the figure below, the data received by the endpoint would be:
```
Name=Value&Address=Value&Email=Value
```
---
# 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://docs.ipaper.io/flipbook-integration/form-integration.md?ask=&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.
